Details
-
Bug
-
Resolution: Fixed
-
Low
-
6.4.14, 7.2.1, 7.1.9, 7.2.8, 7.7.2, 8.5.1
-
6.04
-
39
-
Severity 1 - Critical
-
516
-
-
Description
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Issue Summary
When a custom field configuration is edited and then an issue using that configuration is edited, the custom field values revert to null or the default option.
Users are not likely to notice unless they are attempting to change that field. If they do happen to notice they cannot see the original value in order to restore it to the correct value.
Steps to Reproduce
- Create a Custom Field called "Test" using the "Select List (single choice)" type.
- In the default/Global field configuration, configure three options: A, B, C.
- Create an issue in Project FOO and set the field value to "B".
- Create a new custom field context.
- Configure the same three options for the field in this configuration: A, B, C.
- Configure Project FOO to use this field configuration for the type of issue you created in Step 3.
- Click "Edit" for the issue you created previously.
Expected Results
- After the field configuration is changed, existing values for the field should be preserved unless they cannot be mapped to options in the new configuration.
- Alternatively, JIRA should highlight the modified field values in some way so the user knows they must make a change in the Edit screen.
Actual Results
- If the user does not modify anything on the "Edit" screen and clicks update, the field value will be changed to either 'None' or the first available field option.
- If the field is optional, the field will be set to 'None' in the Edit screen.
- If the field is required, the field will be set to the first available option, not the default option, in the Edit screen.
Workaround
Administrators: After changing the field configuration for a project, for each custom field value you wish to preserve...
- Search for issues that have the custom field set to that value.
- Bulk edit the issues to set them to the correct value in the new field configuration (even if that value matches the default field config)
Detailed description and steps for the workaround are at Change Context for an Existing Custom Field Without Losing Old Data.
Attachments
Issue Links
- causes
-
-
- Needs Triage
-
- has a regression in
-
-
- Closed
-
- is related to
-
JRASERVER-76159 Implement a way to find issues with custom field values that are no longer valid in the custom field context
- Gathering Interest
-
PS-16200 Loading...
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
- is blocked by
-
- Mentioned in
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-