This feature is available in the Advanced edition of the app.
Dynamic Forms features are enabled in Jira Service Management (JSM) projects, provided through support for Customer Portal for company-managed and team-managed projects.
Dynamic Forms works with JSM company-managed and team-managed projects.
Before you configure Dynamic Forms rules for a JSM project, make sure that:
A field must be added to a request type before it becomes visible in the Dynamic Forms fields list. If a field is not assigned to any request type, it will not appear during configuration.
Dynamic Forms rules configured for a JSM project apply to the Customer Portal. When a user fills in a request form on the portal, fields show or hide dynamically based on the configured rules.
Customer Portal is supported for:
The fields available for configuration depend on the fields added to the request types in your JSM project.
The configuration process for JSM projects follows the same mechanism as for other project types - you select a project, enable request types, and then define rules for fields.
In JSM projects, rules are defined per request type and apply when a user submits a request form on the Customer Portal. Each rule consists of:
Rules are evaluated from top to bottom. If a rule’s conditions are met, subsequent rules for the same field are skipped.
For the full list of available actions and how to configure them, see Actions.
Unsaved conditions are marked as Draft next to the field name. You can:
The Dynamic Forms configuration for the JSM project has been created. The rules apply when users fill in request forms on the Customer Portal.
Dynamic Forms for JSM supports a focused set of field types on the Customer Portal. The following fields are available:
| Field | Customer Portal |
|---|---|
| Summary | |
| Description | |
| Text field (single line) | |
| Paragraph (multi-line text) | |
| Single select | |
| Date picker | |
| Number |
Fields such as Labels, Multi select, Cascading select, Priority, User picker, Due date, and Date time picker are not supported in JSM projects. For full field coverage in JSM, use Extension for Jira Service Management.
If you already use or are considering Extension for Jira Service Management, both apps offer Dynamic Forms capabilities for JSM. Dynamic Forms for Jira provides a focused, streamlined experience for showing and hiding fields based on conditions. Extension for Jira Service Management is a more advanced solution with additional features.
| Feature | Dynamic Forms for Jira | Extension for JSM |
|---|---|---|
| Show/hide fields based on conditions | Yes | Yes |
| Customer Portal support | Yes | Yes |
| Company-managed projects | Yes | Yes |
| Team-managed projects | Yes | Yes |
| Validators (required field checks) | Yes | Yes |
| Custom display name per field | Yes | Yes |
| Field help text | Yes | Yes |
| Assets field support | No | Yes |
Use Dynamic Forms for Jira when you need simple, rule-based field visibility in JSM. Use Extension for JSM when you need advanced control over request forms. For more information, see Extension for JSM documentation and the Extension Dynamic Forms overview.
If an instance has two applications that affect fields on work items, only the app installed first will function properly. Do not use both Dynamic Forms for Jira and Extension for JSM to configure dynamic fields on the same JSM project.
Rules using the Current user role condition with contains one of → Service Desk Customer don’t work on the Customer Portal for users who meet all of the following criteria:
Workaround: Use the inverse condition instead: Current user role → does not contain any of → Administrator.
If you can’t find the answer you need in our documentation, raise a support request. Include as much information as possible to help our support team resolve your issue faster.