This collection ensures The Custom Field Health Check is a really useful tool, and we recommend using it regularly. It will help you ensure that the custom fields in your Jira instance are correctly configured and used.
...
There are checks forThe Custom Fields Health Check will run checks against a number of parameters:
| Table of Contents |
|---|
Global custom fields
...
| Info |
|---|
You can find more information about custom field optimization here. |
There are several Several settings that can be configured for this health checkHealth Check:
Minimum number of issues:
The minimum number of issues the custom field has values in for the custom field to be considered optimizable. This allows you to ignore custom fields that are intentionally global but appear to have a local scope simply because they are newer and have not been fully adopted yet.
The default is 50 issues
Maximum number of projects:
The maximum number of projects the custom field has values in for the custom field to be considered optimizable. This allows you to set the threshold at which custom fields are considered effectively global - it can be easier to manage custom fields with them having a global context instead of them having very large contexts with many projects.
The default is 20 projects
Maximum number of issue types:
The maximum number of issue types the custom field has values in for the custom field to be considered optimizable. Again, this allows you to set the threshold at which custom fields are considered effectively global - it can be easier to manage custom fields with them having a global context instead of them having very large contexts with many issue types.
The default is 20 issue types
...
This checks for custom fields that do not have values in any issues - they and are therefore unused.