Appfire's Integrity Check for Jira and Atlassian's Integrity Checker feature comparison
Comparison of Appfire and Atlassian’s integrity check tools
Appfire's Integrity Check for Jira and Atlassian’s Integrity Checker both aim to give administrators assurance that their Jira instances are running smoothly and error-free. The difference between the two is most easily observed through the error detection coverage of your Jira configuration. So, let’s start the comparison and show you what each can offer to improve your Jira system’s stability and efficiency.
Main differences between Integrity Checker and Integrity Check for Jira
We can see a lot of similarities when we first take a quick peek at both Atlassian and Appfire’s app functionalities. However, when we start to dive into more detail, we can see that Jira’s native integrity checker focuses mainly on data integrity. Meanwhile, Integrity Check for Jira extends and complements that functionality by providing error detection for all configuration elements and their attributes.
Feature | Appfire’s Integrity Check for Jira | Atlassian’s Integrity Checker |
---|---|---|
Check for missing objects | Checks for missing objects in more than 20 configuration elements and their attributes (i.e. projects, issue types, workflows, schemes, fields, screens, groups, boards, filters). | Checks for missing objects in 2 configuration elements - field layout schemes and workflows. |
Check for duplicates | Checks all configuration elements for duplicates. | Only checks for duplicate permissions. |
Check for naming inconsistencies | Checks for invalid characters within user names and objects. | Doesn’t check for naming inconsistencies. |
Check for invalid JQLs | Checks all JQLs for errors in all Jira configurations. | Only checks the filter JQLs if they contain any invalid projects. |
Check workflow integrity | Only checks the workflows for errors. | Checks the workflows and current issues' states for errors. |
Check issue relations | Doesn’t check for issue-related errors. | Checks if issues:
|
Check filter subscriptions | Doesn’t check filters for subscription-related errors. | Checks if filter subscriptions have invalid or non-existent triggers and filters. |
Locate configuration errors | Provides path links that navigate to the configuration errors' location. | Doesn’t provide links to the configuration errors' location. |
Quick fix | Fixes certain missing configuration elements (i.e. filters, custom fields, users, groups, sprints). | Fixes certain error types (i.e. issues, searches, duplicate permissions, workflows, fields, and invalid filter subscriptions). |
Integrity Check for Jira has integration with Configuration Manager for Jira (CMJ) and offers snapshot-wide integrity checks.
Learn more about using Integrity Check within CMJ.