Detected integrity errors

This article lists and describes the configuration error types the Integrity Check for Jira app can detect. For example, you can find and resolve duplicate, inconsistent, and missing objects, as well as invalid JQLs and filters. Find the duplicate custom fields in your configuration to speed up your Jira or find the missing objects in filters to improve the experience for your users.

Duplicate object

When there is more than one configuration object of the same type with the same name, this leads to an integrity error. Jira allows only custom fields to be created with the same name. The rest of the configuration element types should have unique names.
Having duplicate configuration elements may lead to inconsistent configuration, causing problems for your Jira users with their daily activities or preventing admins from deploying snapshots with Configuration Manager for Jira.

Solution

Rename the object(s) so all the same type elements have unique names.

Inconsistent object

Inconsistencies with the Jira database can sometimes occur when configuration changes are performed on older Jira versions. It’s also possible that Jira's naming rules cause inconsistencies when an object has forbidden characters in its name. Some examples of other inconsistencies could be mapping issues, missing user data, or missing defaults in a scheme.

Solution

If the issue is that an object has illegal characters in its name, then rename the object. If the default settings of a scheme have been changed after migration, then edit the scheme and ensure defaults are set. For solutions to mapping issues, you can refer to our knowledge base articles. For any other issues with inconsistent objects, contact our support team.

Missing object

A reference to a missing configuration element. For example:

• Notification scheme refers to a "User picker" custom field that is not available on the system.

• Workflow post-function refers to a missing custom field.

You may have multiple configuration objects referring to the same missing object (custom field, for example). In that case, all the errors related to the missing element will be grouped into one error, showing all the references to that object.

Solution

To solve the problem, remove all the references to the missing object or create it so it's available on the system.

Invalid JQL

Invalid JQL can be a part of different configuration elements in Jira. To fix such integrity errors, you first need to correct the invalid JQL. In some cases, you need to edit it directly in the database because you might not be able to perform it from the UI.

Solution

To solve the problem, please correct the JQL entry in the Jira UI. If it is not possible to update it from the UI (you get an error), you need to correct the JQL query directly in the database. For detailed instructions on how to fix invalid JQL entries in different configuration elements, please refer to the following knowledge base article.

Unknown error

An error that does not fall into any of the categories listed above is considered an Unknown error. In that case, you can download a zip file containing information that should help analyze the problem and send it to our support team to help you solve the problem. 

Additional checks

If you need additional checks included in the product, please log an "Additional Integrity Check" issue in our Issue Tracker.