- Introduction
- About
- Get started
- Functionalities
- Fields Visibility
- Translations
- Tabs Visibility
- Mapper
- Secured Fields
- Supported fields
- Bundled Fields
- Overview
- Bundled Fields Configuration
- Using Bundled Fields
- JQL Searcher
- Java API (ScriptRunner)
- Data Sources
- Email notifications
Fields visibility
This page provides information on how to configure Fields Visbility.
You can create conditions upon which a field is displayed after selecting an option in the previous field.
- To set a configuration, log in as a user with Jira Administrators global permission.
- Remember to add all configured fields and custom fields to relevant screens and issue types.
Adding custom fields
Before you start configuring fields you need to add custom fields provided by Dynamic Forms.
- Navigate to Manage Apps > Dynamic Forms > Fields Visibility
- Click Add field or Add new field
- You will be transferred to Jira Custom Fields tab, click Add custom field.
- Select one of the dynamic fields from the list (in the advanced section) and click Next.
- Configure the custom field according to your needs.
Example
- Specify issue types and projects (recommended) or apply to all issues in all projects and click Create.
- Associate the custom field to screens and click Update.
Result
When you go back to the Fields Visibility tab in Dynamic Forms your custom field is present and you can configure it.
Field configuration
Once your custom field has been added you can configure it according to your needs.
- Select related fields - select a field that will show up after selecting the option.
- Required - switch on to make the field (defined in the Related field) required. Related fields can’t be marked as required in the global Jira settings. Otherwise, all Bundled Fields’ subfields would be recognized as required and you wouldn’t be able to differentiate required subfields from optional ones.
Note
- If you’d like to make the entire custom field required, you can do so by setting up a Min. and Max. number of rows. For example, if you set up a Min. number of rows as 1 (or more), it will make it impossible to delete rows on the Create Issue screen and therefore practically make the whole custom field required.
- Jira Toolkit fields shouldn’t be set as required, since their purpose is not to provide any kind of input capability for the user, but to change Jira views with custom HTML.
- Actions - set Tooltip message and Required validation message for language which you want. Click the trash icon to remove settings of selected option.
To make sure that everything works properly, go to the Create Issue screen, choose an option you configured and check if a related field shows up.
We take every effort to make this feature work with any kind of custom field, even those provided by other vendors. However, we can’t guarantee that every non-standard custom field will be supported.
Configuration Details
Empty value - when this option is enabled, None (=empty) value can be selected. To make it disabled, set the state of switch to off. Empty value will not be shown on the list.
Autocomplete - define if the field should be selectable. If you set the state of switch to on, the field will be a text box, which will filter the items. This option is dedicated for the following custom fields provided by Dynamic Forms app: Dynamic Select, Dynamic Multiselect, Dynamic checkboxes, and Dynamic Cascading Select.
Preserve value - when this option is enabled, the last value of the field is stored, so that it will appear upon choosing that option again in the future. It’s particularly useful when a user changes the option but then wants to get back to the former option and remember the value that was chosen for it the last time. This option also affects Jira Custom Fields Default Value. To make it disabled, turn off the toggle and the previous values of the field will always be cleared.
Field width - define the field width in pixels. If this field is empty, the default value of field width will be set.
If you can’t find the answer you need in our documentation, raise a support request.