Overview

The Integrity Checker tab provides the capability to Check or immediately Recover inconsistencies on

• the Data maintained by the App, so to ensure that any update performed on the Jira core tables is consistent with the data persisted on the app tables
• the Approval Conditions on the Workflows interested by the Approvals configurations
• the Project Permissions on the Permission Scheme interested by the Approvals configurations (Browse Projects, Transition Issues, Resolve Issues, Close Issues)
• the Automatic Actions (e.g. automatic notification and automatic workflow transition), so to ensure that, basing on the applied configurations, any expected automatic action, that for some reason were not performed, can succeed.

Furthermore, following a Check or a Recover, the app log into the Integrity Check Log file and the Integrity Recover Log file which anomalies have been identified and how the app have recovered them.

Integrity Check

• Choose  > Manage apps > Herzum Approval >Troubleshooting and Support. 
• Select the Check box.
  The Integrity checker has a number of 'integrity checks' that look for common inconsistencies in
  • Herzum Approval's stored data
  • Jira Data impacting app functionalities (Approval Conditions on the Workflows,  Project Permissions)
  • Issues Workflow status with respect any expected automatic workflow transition to perform
  • Approvals Notifications with respect any expected automatic notification by email or by Comments.

• Select one or more items whose data you would like to check the integrity of and click the 'Check' button.
• After the selected checks run, the screen provides details about the existing inconsistencies. (The whole list of possible inconsistencies by 'integrity checks' type can be reviewed on List of possible inconsistencies by 'integrity checks')
• If any inconsistencies were found, you are able to fix it navigating on the Recovery tab or fix it manually basing on the reported information. 
• If any inconsistencies were found you will be able to retrieve these information on the integrityCheck log file.

 Notice that this file is overwritten each time that you run the check. Case you want maintain these information for future review, you must download the file and keep it in a different folder. 

Integrity Recover

• Choose  > Manage apps > Herzum Approval >Troubleshooting and Support. 
• Select the Recove box.

 The Integrity recover performs the same 'integrity checks' then the Intergrity Checker, but, in addition, it fixes the inconsistencies.

• Select one or more items whose data you would like to recover the integrity of and click the 'Recover' button.

 Some of the 'recover integrity operations' have depends by the consistency of other recovers so it's not possible to recover them without perform a recover of an item that can potentially impact it. The app automatically manage such dependency by checking the related box.

• After the selected checks run, the screen provides details about the existing data inconsistencies and all the corrective actions that have taken place.

 We strongly recommend taking a backup of your data before correcting any data inconsistencies.

You are able to recover data integrity and automatic actions consistency on any distinct item listed below:

• Recover Core Approval Configurations Data Integrity

  • Recover Approval Mapping Configurations Integrity: The routine recovers database consistency by deleting any any Approval Mapping associated to a Project, Issue type, Source Workflow status Id and Workflow Transition ID that doesn't exist anymore or case of the configuration is not consistent with respect the workflow configuration.

  • Recover Single Issue Approval Configurations Integrity: The routine recovers database consistency by deleting any any Single Issue Approval Configurations associated to an Issue Id, Source Workflow status Id and Workflow Transition ID that doesn't exist anymore or case of the configuration is not consistent with respect the workflow configuration.

  • Recover the Minimum Required Approvals based on conditions consistency: The routine recovers database consistency by deleting any "Minimum Required Approvals based on conditions" configuration associated to an Approval Mapping ID or Issue Id that is not defined or case of the associated Approval Mapping Id or Issue Id doesn't exist anymore. 

  • Recover Conditional Rules: The routine recovers database consistency by updating the User Evaluator setup on any Conditional Rule when it is found null or empty.

• Recover Pending Approvals Integrity

  • Recovery consistency on All Issue Approval

• Recover Non-Core Approval Configurations Data Integrity

  • Recover on Permissions to notify an Approval Request

  • Recover on Permissions to Configure Approval for Single Issue

  • Recover Users list separator

  • Recover Template Icon

• Recover Jira Data impacting automatic transition

  • Recover Automatic Reponsive Transition permissions

• Recover Jira Data impacting app functionalities
  
  • Recover Approval Conditions on the Workflows

• Recover Automatic actions consistency

  • Recover Automatic Transition Consistency

  • Recover Approval Request email notification consistency

  • Recover Approval Request by Comment consistency

 The App doesn't allow to run the Recover of the Automatic Actions without running the Recovery of Core Data Integrity.