Overview

You are able to run the check integrity on any distinct 'integrity check' listed below:

• Check Core Approval Configurations Data Integrity
  • Check Approval Configurations Integrity: The routine checks if any Approval's Property is set with a no more valid value.

  • Check Approval Mapping Configurations Integrity: The routine checks if any Project, Issue type, Source Workflow status Id and Workflow Transition ID associated to any Approval Mapping doesn't exist anymore and if they are not consistent with respect the workflow configuration.

  • Check Single Issue Approval Configurations Integrity: The routine checks if any Approval Id, Issue Id, Source Workflow status Id and Workflow Transition ID associated to any Approval Mapping doesn't exist anymore and if they are not consistent with respect the workflow configuration.

  • Check the Minimum Required Approvals based on conditions consistency: The routine checks if any "Minimum Required Approvals based on conditions" is associated to an inconsistent Approval Mapping ID or Issue Id. 
  • Check Conditional Rules: The routine checks if the User set to evaluate the Conditional Rules (The Conditional Rule Super User) is valid and if this user has the expected privileges allowing the app to work as expected.
• Check Pending Approvals Integrity
  • Check consistency on all pending approvals: Check Pending Approvals integrity with respect to either the Approval Mapping Configurations and the Single Issue Approval Configurations.
• Check Non-Core Approval Configurations Data Integrity

  • Check on Permissions to Notify an Approval Request: The routine checks if any Project and Issue type associated to the Permissions to 'Notify an Approval Request' doesn't exist anymore. 

  • Check on Permissions to Configure Approval for Single Issue: The routine checks if any Project and Issue type associated to the Permissions to 'Configure Approval for Single Issue' doesn't exist anymore. 

  • Check Users list separator: The routine checks on the Users field value of the Approvals table in order to ensure that the used convention to concatenate the list of users is the expected one.
  • Template Icon: The routine checks if any email template has an associated invalid icon (Icon Id = null). 
• Check Jira Data impacting automatic transition
  • Check Automatic Responsive Transition permissions: The routine checks if the Super User running the Responsive Automatic Transition has Transition Issue permission on any Project interested by an Approval Mapping configuration or a Single Issue approval configuration.
• Check Jira Data impacting app functionalities
  • Check Approval Conditions on the Workflows:  The routine checks the existence of the Approval condition on any workflow transition belonging to the workflows used by the Projects/Issue Types interested by an Approval Mapping configuration or used by the issues interested by a Single Issue approval configuration. 
• Check Automatic actions consistency

  • Check Automatic Transition consistency: The routine checks if some issue had not transited automatically

  • Check Approval Request email notification consistency: The routine checks if the Outgoing SMTP Mail Server is enabled and if any expected  automatic approval request notification was not sent by email. 

  • Check Approval Request by comment consistency: The routine checks if any expected  automatic approval request notification was not sent by Jira Comments 

Check Approval Configurations Integrity

The routine checks, for each configured Properties values (e.g. Roles, Groups, Users, User Pickers, Group Pickers).

The following is the list of possible inconsistencies that the routine is able to intercept:

• The Approval (Id XX) is inconsistent. The following Roles do not exist anymore: ABC. The following User Pickers do not exist anymore: customfield_XXX.
• The Approval (Id XX) is inconsistent. The following Groups do not exist anymore: ABC.
• The Approval (Id XX) is inconsistent. The following Users do not exist anymore: ABC.
• The Approval (Id XX) is inconsistent. The following User Pickers do not exist anymore: customfield_XXX.
• The Approval (Id XX) is inconsistent. The following Group Pickers do not exist anymore: customfield_XXX.

Any of the inconsistency above relates to cases where the previous configured values are no more valid because they have been updated or deleted in Jira.

Check Approval Mapping Configurations Integrity

The routine checks, for each configured Approval, the consistency of the configured Project, Issue Type, Source Workflow Status, Workflow Transition.

The following is the list of possible inconsistencies that the routine is able to intercept:

• The Approval Mapping (Id XX) is inconsistent because The issue type (Id YY) is not associated to the project (Id ZZ).
• The Approval Mapping (Id XX) is inconsistent because The project (Id YY) does not exist.
• The Approval Mapping (Id XX) is inconsistent because Source Status (Id YY) does not exist in the Workflow ABC for the Project DEF.
• The Approval Mapping (Id XX) is inconsistent because Transition (Id YY) is not related to the status ABC.

Check Single Issue Approval Configurations Integrity

The routine checks, for each configured Approval, the consistency of the configured Source Workflow Status, Workflow Transition.

The following is the list of possible inconsistencies that the routine is able to intercept:

• The Issue Approval (Id XX) is inconsistent because the issue (Id YY) does not exist.
• The Issue Approval (Id XX) is inconsistent because Transition (Id YY) is not related to the status ABC.
• The Approval (Id XX) set on the Single Issue Approval configuration (Id YY) doesn't exist.
• The Issue Approval (Id XX) is inconsistent because Transition (Id YY) is not related to the status ABC.
• The Issue Approval (Id XX) is inconsistent because Source Status (Id YY) does not exist in the Workflow DEF.

Check the Minimum Required Approvals based on conditions consistency

The routine checks , for each configured "Minimum Required Approvals based on conditions" the consistency of the associated Approval Mapping ID or Issue Id.

The following is the list of possible inconsistencies that the routine is able to intercept:

• The Issue (Id XX) doesn't exist. The Approval MRA (Id = YY) based on Condition configured for this issue is not applicable.
• The Approval MRA (Id = XX) is associated with a mapping configuration not valid.

Check Conditional Rules

The routine checks if the User set to evaluate the Conditional Rules (The Conditional Rule Super User) is valid. It includes to check if the user exists and if it is an active user.

Furthermore, the routine checks, for any project, if this user has browsing privileges on them.

The following is the list of possible inconsistencies that the routine is able to intercept:

• The Super User ABC is not active.
• The user ABC does not have permission to browse issues on the DEF permission scheme.
• The Super User used to evaluate Conditional Rules does not exist.

Check consistency on all pending approvals

The routine checks the consistency of the existing Pending Approvals with respect to the Approval Mapping Configurations or Single Issue Approval Configurations.

The following is the list of possible inconsistencies that the routine is able to intercept.

Case of a pending Approval is inconsistent with respect Single Issue Approval Configuration, you are advised by one of the following messages:

• The Approval (Id XX) set on the Single Issue Approval configuration (Id YY) doesn't exist.
• The Workflow Transition (Name: ABC) associated to the Pending Approval (Id: XX) for the issue (Key: DEF) doesn't match the Workflow Transition (Name: GHI) associated to the configured Source Status (Id: YY).

Case of a pending Approval is inconsistent with respect an Approval Mapping Configuration, you are advised by one of the following messages:

• The Issue Approval (Id XX) for issue (ABC) is inconsistent because the Source Status (Id YY) doesn't match any Approval Mapping configuration.
• The expected pending Approval (Name ABC) on the Issue (Key ABC is inconsistent.
• The Issue Approval (Id XX) for the issue (Key ABC) is inconsistent because the Advanced settings do not correspond to those of the Mapping 
• The Issue (Id XX) set on the Issue Approval (Id = YY) does not exist.
• The Issue Approval (Id XX) for the issue (Key ABC) is inconsistent because it does not relate to a Single issue Approval Configuration and neither to an Approval Mapping
• The Workflow Transition (Name: ABC) associated to the Pending Approval (Id: XX) for the issue (Key: DEF) doesn't match the Workflow Transition (Name: GHI) associated to the configured Source Status (Id: YY).

Check on Permissions to Notify an Approval Request

The routine checks if any Project and Issue type associated to the Permissions to 'Notify an Approval Request' doesn't exist anymore. 

The following is the list of possible inconsistencies that the routine is able to intercept:

• The Permissions to display the Request Approval button by Project and Issue type include the Project (Id XX) that does not exist anymore.
• The Permissions to display the Request Approval button include the Project (Id XX) that does not exist anymore.
• The Permissions to display the Request Approval button by Project and Issue type include the Issue Type (Id XX) that does not exist anymore.

Check on Permissions to Configure Approval for Single Issue

The routine checks if any Project and Issue type associated to the Permissions to 'Configure Approval for Single Issue' doesn't exist anymore. 

The following is the list of possible inconsistencies that the routine is able to intercept:

• The Permissions to Configure Approvals for Single Issue by Project and Issue type include the Project (Id  XX) that does not exist anymore.
• The Permissions to Configure Approvals for Single Issue Enabled Projects include the Project (Id XX) that does not exist anymore.
• The Permissions to Configure Approvals for Single Issue by Project and Issue type include the Issue Type (Id XX) that does not exist anymore.

Check Users list separator

The routine checks on the Users field value of the Approvals table in order to ensure that the used convention to concatenate the list of users is the expected one.

The following is the list of possible inconsistencies that the routine is able to intercept:

• The Approval ABC has unexpected user list separator.

Template Icon

The routine checks if any email template has an associated invalid icon (Icon Id = null). 

The following is the list of possible inconsistencies that the routine is able to intercept:

• No icon has been set as Logo on the template (Id XX).

Check Automatic Responsive Transition permissions

The routine checks if the Super User running the Responsive Automatic Transition has Transition Issue permission on any Project interested by an Approval Mapping configuration or a Single Issue approval configuration.

The following is the list of possible inconsistencies that the routine is able to intercept:

• The user DEF does not have permission to transition issues on the ABC permission scheme.
• The user DEF does not have permission to resolve issues on the ABC permission scheme.
• The user DEF does not have permission to close issues on the ABC permission scheme.

Check Approval Conditions on the Workflows

The routine checks the existence of the Approval condition on any workflow transition belonging to the workflows used by the Projects/Issue Types interested by an Approval Mapping configuration or used by the issues interested by a Single Issue approval configuration.

The following is the list of possible inconsistencies that the routine is able to intercept:

• The Approval Condition must be added on the transition ABC in the workflow DEF.
• The app doesn't recover Approval Conditions when Approval Condition Settings is set to Off

Check Automatic Transition consistency

The routine checks if some issue had not transited automatically.

Check Approval Request email notification consistency

The routine checks if the Outgoing SMTP Mail Server is enabled and if any expected  automatic approval request notification was not sent by email. 

The following is the list of possible inconsistencies that the routine is able to intercept:

• Outgoing Mail is Disabled

Check Approval Request by comment consistency

The routine checks if any expected  automatic approval request notification was not sent by Jira Comments.