I am working on auditing all of our fields in our Jira environment and deleting potential duplicates.
I'm noticing cases where a field shows:
However, when I run a JQL query against that same field, I can find issues that still contain values in the field.
In situations where the field administration page and JQL results appear to conflict, which source should be considered authoritative?
Specifically:
Welcome to the Community.
In general from my experience, the field configuration page in the admin UI gives you the current stats... However, you may very well having old historical data in your system from your JQL result.
Example - Field A was originally setup for a given project and it was used, however later on the field itself was removed from the project and screen.
I would always trust the field side configuration + looking for JQL results for confirmation (to determine how important are the field values associated to issues in your JQL results, and then determine if the field should be deleted from the system.
In our env, historical data is important, thus we may choose to renamed the field appending "(Old)" before deleting the field. This gives the end users (content owners) times to evaluate if the field information is needed or not. Afterward, we proceed with the action (i.e. delete the field or keep the field).
Hope this helps.
Best, Joseph
The field might have been on screens and used historically or an automation/api has filled the field within issues.
Then not all fields do not have to be on a screen, but will be updated.
Or has this been migrated from another site or it was created on a CVS import.
All above are options, then it can still say the Date Last used is empty, no screen, no context.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.