-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
2
-
Severity 3 - Minor
Summary
- For a custom field of type Select List (single choice) that has two (2) values A and B.
- After adding the context and specifying the default value as "A" we are expecting it to be populated to the next created issues and also for editing the existent issues.
- But, currently it afect the new issues but break the default value for editing the existent issues.
Steps to Reproduce
1. Create a custom field drop down called Spaceteam
2. Populate with options A, B
3. Add the custom field to the create and resolve Screens
4. Create an issue in project "Gokoko" and select option B for the custom field
5. Go back to the custom field Spaceteam and add a context
6. Duplicate the list of options from the parent custom field into the new context
7. Set the default to the context as option A
8. Set the assigned project Gokoko for this context
9. Go back to the issue created in step 4 and click on the Edit Issue button
10. Observe the custom field
11. Back out of the edit screen
12. Resolve the issue so the resolve issue screen pops up
13. Observe the custom field
Expected Results
- Custom field is populated with option B set in step 4
Actual Results
- Custom field is unpopulated
- value "None" is shown by default
- is related to
-
JRACLOUD-70999 Concurrent issue edition with custom field's context change
-
- Closed
-