Analyzing the usage of custom fields
Having too many custom fields can clutter your Jira instance and affect its performance. It’s normal for these fields to grow over time, as admins create testing fields, duplicates, or fields that are no longer used. However, monitoring and cleaning up your fields is necessary to keep your instance quick and healthy. This page explains some of the tools you can use to analyze the usage of your custom fields to decide if they’re still needed.
Finding custom fields that are no longer used
The Issues column shows you the number of issues that store a value for your field, and includes both issues with default values and archived issues.
Click the column name to sort in ascending or descending order.
Custom fields with a low number of issues are the most likely candidates for deletion. If you’re not sure if a field should be deleted or not, use other columns described here to make your decision.
Good to know
Data in this column is refreshed once a day. You can see the date of the last refresh above the column (Issues: last refresh…)
Data won’t be available for around 24 hours after the upgrade.
Finding custom fields that haven’t been updated for a long time
The Last value update column shows you the last time a value for a custom field has been added or updated in any issue, but it doesn’t include default values—as in, the user must actively choose or add a value for this field.
Filter your issues by Last value update to find custom fields that haven’t been updated for a long time. We consider 2 years to be quite old, but this will depend on you.
Check the Issues column to see how many issues are using this field.
If the fields are outdated, but still used in thousands of issues, this might mean they’re still important. If you’re not ready to delete them, you could improve performance by narrowing down their context only to the projects they’re used in.
Good to know
Data in this column is refreshed every hour, but the historical data about the usage of custom fields in existing issues won’t be available for around 24 hours after the upgrade. Any new updates you make after upgrading will be available right away.
If you’re importing a project or just need to recalculate this data as a fallback method, you can recalculate it in Jira advanced settings.
Comparing to other columns to help you make the decision
Issues and Last value update are the best tools to identify fields that are a bit rusty, but not all such fields should be deleted. Some of them might store data from your past projects that you’d like to keep for reference. This is where other columns should help you.
Shows specific projects that can use this field, or Global if the field is allowed for all projects. This should help you decide how important your field is.
Good to know
Check the Last value update for your field. If it hasn’t been used for a long time but you’d like to keep the data it contains, narrow it down to the projects it’s been used in in the past.
Shows the screens where your custom field is displayed, like a Create issue screen or Default issue screen. The number of screens using your custom fields, and what screens those are, should help you decide whether it’s really needed.
If you’re on a mission to clean up your Jira instance and keep it that way, here are some useful pages: