-
Bug
-
Resolution: Fixed
-
Low
-
8.20.2, 8.13.18
-
None
-
8.13
-
6
-
Severity 2 - Major
-
5
-
Issue Summary
https://confluence.atlassian.com/adminjiraserver/optimizing-custom-fields-956713279.html
Steps to Reproduce
- Create a new field and use the field in an issue ticket
- Archive that issue ticket. At this point, the only issue that had used the field is archived. No other issues are using this field
- Run the Custom field optimizer
- Click "Manage these custom fields"
- Notice that this new field is saying that it is "Used by" "0 project"
Expected Results
The results will still show that the field is "Used by" "1 project"
Actual Results
The new field is saying that it is "Used by" "0 project"
- This is a concern as administrators will believe that the field is not used at all and delete the field. This will result in all tickets, including the archived tickets, to lose any values stored for that field.
Workaround
None
- is duplicated by
-
JRASERVER-74669 Jira custom field optimizer fails on fields used on issues of archived projects
- Closed
- relates to
-
JRASERVER-77748 Custom field optimizer doesn't show projects with archived issues after running a scan
- Gathering Impact
-
FLASH-3807 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...