-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Medium
-
None
-
1
-
Severity 3 - Minor
Issue Summary
Configuring a Dependent dropdown (aka Cascade) type custom field in a Jira team-managed space and setting a default value does not save the value. This is evident when creating a Jira work item and observing the custom field value. The default value is neither saved in the Create or View work item operation.
Steps to Reproduce
- Navigate to a Jira team-managed space > Space settings > Work types and select a work type
- Create a Dependent dropdown field with some options/values
- Select the default option/value and save changes
- Create a new work item in the team-managed space and observe that the default option/value configured in step 3 doesn't appear
Expected Results
The default option/value configured for the field should be saved and appear when creating or viewing a work item in a team-managed Jira space
Actual Results
The value of the Dependent dropdown field is empty and doesn't show the saved default option/value.
Workaround
- Create a Cascade-type field from the global field context (Settings > System > Work items > Fields)
- Once the field has been created, navigate to the field, click on the 3 dots below the Actions column and select 'Contexts and default values'
- Configure the Options and then subsequently the default value
- Ensure that the 'Applicable contexts for scheme' shows Global (all work items)
- Navigate to your Jira team-managed space > Space settings > Fields > Add field and add the newly created Cascade-type field
- Navigate to the work type, drag-and-drop the Cascade-type field to to either the Context or Description fields and save changes