Issue Summary

At present, the optimizer only recognizes projects' usage of a custom field if the custom field is populated in a Jira ticket.  The optimizer will mistakenly recommend removing the field for newly created projects (having no tickets) or projects with tickets whereby the custom field is unpopulated.

Steps to replicate: Case 1

1. Create a new project to include a custom field.
2. Run the Custom Fields Optimizer
3. Observe that it shows the custom field as unused. 
4. Applying optimizer “Change context” will result in custom field becoming unavailable.

Steps to replicate: Case 2

1. Create a new project to include a custom field on a Resolved screen.
2. Create a ticket.  Do not resolve ticket.
3. Run the Custom Fields Optimizer
4. Observe that it shows the custom field as unused. 
5. Applying optimizer “Change context” will result in custom field becoming unavailable.

Work-around

There is no workaround available at present.