Issue Summary

When running the Custom Field Optimizer (CFO), it won't show that projects with archived issues are using the target custom field, nor that they may be part of the change applied by the optimizer.

Steps to Reproduce

1. Install a vanilla instance of Jira Software Data Center.
   • This was validated on versions 9.6, 9.12, 9.15 and 9.16.
2. Create two Scrum software projects with sample data.
   • In this example these projects are KANBAN1 and KANBAN2.
3. Create a custom field with global context and assign it to screens associated to projects KANBAN1 and KANBAN2.
4. Add values to this custom field on a couple of issues from KANBAN1 project and then archive these issues.
   
5. Add values to this custom field on a couple of issues from KANBAN2 project and then archive the project.
   
6. Go to Administration > Issues > Custom fields optimizer.
7. Click on Scan custom fields.
8. Within the scan results, click on Manage these custom fields.

Expected Results

The CFO results shows the target custom field with a global context and shows it is being used within 2 projects. That way, the administrator knows the action will consider these two projects.

Actual Results

The CFO results shows the target custom field with a global context and shows it is being used within 0 project.

This UI may give the administrator the wrong perception this custom field isn't used within the Jira instance.

Clicking on the Change context action, and then confirming it, CFO will actually consider both projects on the change.

Checking the changes made by the CFO action shows that both projects were added to the newly created context.

This action is expected, but Jira doesn't show anywhere on the UI it will be carried out, hence being confusing to administrators.

This is a problem since JRASERVER-73207 was fixed, on which CFO started to consider archived issues.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.