Health Checks are a great way to identify problems in Jira and save the time of your Jira Administrators. Optimizer for Jira comes with over 20 health checks which can be used to analyze your Jira instance and show warnings or errors when something is detected that is considered bad practice or incorrect.
Health checks are displayed as cards on the homepage of Optimizer for Jira with green, yellow, or red color indicating pass, warning, or error status, respectively.
View available Health Checks
To view a list of available health checks in a specific category (e.g., Warning, Failed, etc.), click on a section of the chart, or the 4 badges on the page.
By clicking on the Total badge you will get a detailed list of all checks.
View the Health Check details
By clicking on a health check card you can view specific details about the warning or error. This is shown in the screenshot on the right.
By clicking on a row in the view showing the failures and warnings, you can deep dive to either fix the issue or to find out more information about the detected problem.
Available Health Checks
Optimizer for Jira comes with a wide range of health checks, as detailed below:
Resolution Named Unresolved
Duplicate Workflow Scheme names
Duplicate Workflow names
Duplicate Status names
Duplicate Screen Scheme names
Duplicate Screen names
Duplicate Resolution names
Duplicate Issue Type Screen Scheme names
Duplicate Issue Type Scheme names
Duplicate Issue Type names
Duplicate Custom Field names
Unused Custom Fields - Optimizer will highlight any fields that are “Unused”. The definition of an Unused Custom Field is one that has no issues associated with it but may still have screens and workflows. We recommend a Jira administrator reviews these Custom Fields on a case by case basis before making any decisions.
Global Custom Fields
Too many Permission Schemes
Small and Empty Projects - Small projects do not include empty projects. Empty projects are those with 0 issues and small projects are those with between 1 and 10 issues (inclusive), and the two are separate from each other. There is no consideration of when the project was created in this health check
Inactive Projects - performs a JQL search of the form
updated >= -60d(where 60 is the default number of days, and can be configured) to find projects where no issue has recently had the
updatedfield modified. This field is modified by any change to an issue such as editing the summary or description, logging time, moving etc. See the Jira docs for more info. With this definition, newly created projects are considered inactive since they have no issues
Inactive or Removed Leads
Default Issue Type Scheme Usage
Built-in backup disabled on large system
Health Check Scheduling
The health checks in Optimizer for Jira run separately from any tasks in the Task Manager and it is not possible to set custom scheduling within the App itself.
If you need to change the frequency, this can be done in the database itself and we would only recommend changing the scheduling if absolutely necessary. Please contact our support team for assistance with this.