Overview

The Dependencies Analyzer Tab allows to identify the Jira entities (Projects, Issue Types, workflow statuses, transitions, Users, Groups, Project roles etc) used or referenced by the Approval Configurations in the local instance.

This information allow the Administrator to check if the target Jira instance have the needed entities allowing to achieve a successful import.

The form allows to

• export a dependencies analysis report
• display the result of the dependencies analysis out-coming

On clicking Launch, the app identifies, for each Approval table that stores the Configurations applied on the source instance, the Jira entities that are referenced by this table.

 It is strongly recommended to run the Dependency Analyzer after that you have performed an Approval Recovery in order to ensure that data on the Source instance are consistent.

The app will delete any dirty data (tuples having  Export status = Draft) before to start the Dependencies Analysis.

Dependencies Analyzer Output

After that the dependency analysis complete, you will be able to display the Jira entities referenced by any Approval table and Download the Dependencies Report.

Note: On the right is the result of the analysis, if you click on a button you will see the specific result expanded in the list

The Download Dependencies Report button allows to download a file that lists for each entity the dependency analysis result.

The Report will include any message displayed on the form.

Dependencies Analyzer messages

By following a dependency analysis there are three type of messages that can be displayed:

• Info: these messages report information that doesn't require any action by the sys admin.
• Warnings: these messages report relevant information that the sys admin must use in order to prepare the target instance with all the Jira entities referenced by the Approval Tables.

 Notice that on performing the Approval Data import, the app will search referenced entities by usernames (for user key data) and by Name (for other entities, e.g. Project Name, custom field Name, etc.).

• Error: these messages report the missing Jira entities referenced by the Approval Tables. Such errors must be fixed before to perform the Approval Data export in order to allow the operation to succeed. The Approval recovery is able to fix the inconsistencies automatically.

The messages that can be displayed by type per table are listed below.

AO_D195E9_LANG_PACK_KEY_VAL

Info

• result: OK
• result: No Data

AO_D195E9_LANGUAGE_PACK

Info

• result: No Data

Warning

• Modified_User: admin. Username admin must exist on the target instance.

AO_D195E9_APPROVAL_HISTORY

Info

• The Approval History analysis was not performed because data will not included into ApprovalDataExport file

AO_D195E9_NTF_SCHEME_DETAIL

Info

• result: OK
• result: No Data

Warning

• NOTIFY_EXPRESSION: <include><users>admin, test</users></include><exclude></exclude>. Usernames admin, test must exist on the target instance.

Error

• NOTIFY_EXPRESSION: <include><users>admin, test</users></include><exclude></exclude>. Usernames admin, test do not exist.

AO_D195E9_NTF_SCHEME

Info

• result: OK
• result: No Data

AO_D195E9_ISSUE_APPROVAL

Info

• The Issue Approval analysis was not performed because data will not included into ApprovalDataExport file

AO_D195E9_APPROVAL_DEFINERS

Info

• result: No Data

Warning

• Definer: admin; Type:User. Username admin must exist on the target instance.
• Definer: Test; Type: Group.  Group Test must exist on the target instance.
• Definer: TestR; Type: Role.  Role TestR must exist on the target instance.
• Project_Id: 10005 Issue_Type: 10208. Issue Type Demo Test for Project Demo Project must exist on the target instance.

Error

• Project: Id 10003. The Project doesn't exist 
• Issue Type: Id 10007. The Issue Type doesn't exist 

AO_D195E9_APPROVAL_DELEGATED

Info

• result: No Data

Warning

• Delegated key: JIRAUSER10102. Username admintest must exist on the target instance.
• Delegator key: JIRAUSER10112. Username newtest test must exist on the target instance.
• Project_Id: 10005 Issue_Type: 10208. Issue Type Demo Test for Project Demo Project must exist on the target instance.

Error

• Delegated key: JIRAUSER10132. Userkey doesn't exist
• Delegator key: JIRAUSER10142. Userkey doesn't exist
• Project: Id 10003. The Project doesn't exist 
• Issue Type: Id 10007. The Issue Type doesn't exist 

AO_D195E9_APPROVAL_MENU_PERM

Info

• result: No Data

Warning

• User: JIRAUSER10102. Username admintest must exist on the target instance.
• Goup: admintest. Group admintest must exist on the target instance.

Error

• Delegated key: JIRAUSER10132. Userkey doesn't exist
• Goup: admintestb. Group admintestb doesn't exist

AO_D195E9_APPROVAL_MRA

Info

• result: No Data
• Only tuples referencing an Approval Mapping will be exported

Warning

• SOURCE_STATUS_ID: 1002. TRANSITION_ID: 1004. Workflow transition Approve outgoing from Workflow status To Do must exist on the target instance.

Error

• SOURCE_STATUS_ID: 1001. The Workflow status doesn't exist
• TRANSITION_ID: 1001. The Workflow transition doesn't exist

AO_D195E9_APPROVAL_NOT_NOTIFY

Info

• result: No Data

Warning

• USER_PICKER customfield_10117. The Custom-field  Approvers must exist on the target instance.
• USER testuser.  The Username testuser must exist on the target instance.
• GROUP Gtest . The Group Gtest must exist on the target instance.
• ROLE Administrators. The Project Role Administrators must exist on the target instance.

Error

• USER_PICKER customfield_10117. The Custom-field doesn't exist
• USER antonella.capalbo.  The Username doesn't exist
• GROUP jira-administrators. The Group doesn't exist
• ROLE Administrators. The Group doesn't exist

AO_D195E9_APPROVAL_PROJECTS

Info

• result: No Data

Warning

• Project_Id: 10005. Project Demo must exist on the target instance.

Error

• Project: Id 10003. The Project doesn't exist 

AO_D195E9_APPROVAL_RECIPIENTS

Info

• result: No Data

Warning

• USER_PICKER customfield_10117. The Custom-field  Approvers must exist on the target instance.
• USER JIRAUSER10100.  The Username test.test must exist on the target instance.
• GROUP Gtest . The Group Gtest must exist on the target instance.
• ROLE Administrators. The Project Role Administrators must exist on the target instance.

Error

• USER_PICKER customfield_10117. The Custom-field doesn't exist
• USER JIRAUSER10100.  The Userkey doesn't exist
• GROUP jira-administrators. The Group doesn't exist
• ROLE Administrators. The Group doesn't exist

AO_D195E9_APPROVAL_REQUESTERS

Info

• result: No Data

Warning

• USER testuser.  The Username testuser must exist on the target instance.
• GROUP Gtest . The Group Gtest must exist on the target instance.
• ROLE Administrators. The Project Role Administrators must exist on the target instance.
• Project_Id: 10005 Issue_Type: 10208. Issue Type Demo Test for Project Demo Project must exist on the target instance.

Error

• USER antonella.capalbo.  The Username doesn't exist
• GROUP jira-administrators. The Group doesn't exist
• ROLE Administrators. The Group doesn't exist
• Project: Id 10003. The Project doesn't exist 
• Issue Type: Id 10007. The Issue Type doesn't exist 

AO_D195E9_APPROVAL_SEQUENCE

Info

• result: No Data

Warning

• USER JIRAUSER10100.  The Username test.test must exist on the target instance.

Error

• USER_KEY: JIRAUSER10132. Userkey doesn't exist

AO_D195E9_AUTO_TRANSITION

Info

• The AUTO_TRANSITION analysis was not performed because data will not included into ApprovalDataExport file

AO_D195E9_CONFIG_PROPERTIES

Info

• result: OK

Warning

• REV_ACT_USERS admin, test.test. The Usernames admin, test.test must exist on the target instance.
• APP_EXPR_SU admin. The Usernames admin mu st exist on the target instance.

Error

• REV_ACT_USERS admin, test.test. The Usernames admin, test.test don't exist
• APP_EXPR_SU admin. The Usernames admin doesn't exist

AO_D195E9_APPROVAL_MAPPING_REL

Info

• result: OK
• Locked data will not be imported

AO_D195E9_APPROVAL_MAPPING

Info

• result: OK

Warning

• AREA_DATE_PICKER: customfield_10127. The Custom-field  Test must exist on the target instance.
• AREA_SERVICE_NAME: ApprovalRequestAutomation. The Service having Name ApprovalRequestAutomation Class com.herzum.approval.service.email.ApprovalRequestAutomation type must exist on the target instance.
• DA_SERVICE_NAME: ApprovalActionAutomation. The Service having Name ApprovalActionAutomation Class com.herzum.approval.service.email.ApprovalActionAutomation type must exist on the target instance.
• DA_USER_KEY: JIRAUSER10108. The Username testuser must exist on the target instance.
• Project_Id: 10005 Issue_Type: 10208. SOURCE_STATUS_ID: 10005. TRANSITION_ID: 1004. TRANSITION_ON_REJECTING: 10064. DESTINATION_STATUS_ID: 10006.  Issue Type Demo Test for Project Demo Project must exist on the target instance and the assigned workflow must have the Workflow transition Approve (having as destination status Done) and the Workflow transition Reject outgoing  from the Status ToDo
• SUPER_APPROVERS_EXPRESSION: <include><users>admin, test</users></include><exclude></exclude>. Usernames admin, test must exist on the target instance.

Error

• AREA_DATE_PICKER: customfield_10127. The Custom-field doesn't exist.
• DA_USER_KEY: JIRAUSER10108. The Userkey doesn't exist.
• DESTINATION_STATUS_ID: 10006. The Status doesn't exist.
• SOURCE_STATUS_ID: 10005. The Status doesn't exist.
• Project: Id 10003. The Project doesn't exist 
• Issue Type: Id 10007. The Issue Type doesn't exist 
• SUPER_APPROVERS_EXPRESSION: <include><users>admin, test</users></include><exclude></exclude>. Usernames admin, test do not exist.
• TRANSITION_ID: 1004. The Workflow transition doesn't exist
• TRANSITION_ON_REJECTING: 10064. The Workflow transition doesn't exist

O_D195E9_APPROVAL

Info

• result: No Data

Warning

• Groups: Test, Testx TestTest.  Groups Test, Testx, TestTest must exist on the target instance.
• Group_Picker: customfield_10117. The Custom-field  Test must exist on the target instance.
• Roles: TestR, Testxr TestTestR. Project Roles TestR, TestxR, TestTestR must exist on the target instance.
• Users: jirauser10101, jirauser10101, jirauser10102. Usernames admintest, demouser, Undefined  must exist on the target instance.
• User_Picker: customfield_10117. The Custom-field  Test must exist on the target instance.
• USER_PICKER_ALL_EXPR: <include><users>admin, test</users></include><exclude></exclude>. Usernames admin, test must exist on the target instance.
• User_Picker_Any: customfield_10117. The Custom-field  Test must exist on the target instance.
• USER_PICKER_ANY_EXPR: <include><users>admin, test</users></include><exclude></exclude>. Usernames admin, test must exist on the target instance.

Error

• GROUP_PICKER: customfield_10118. The Custom-field doesn't exist.
• Users: jirauser10102. Userkey doesn't exist.
• User_Picker: customfield_10115. The Custom-field doesn't exist.
• User_Picker_Any: customfield_10115. The Custom-field doesn't exist.

AO_D195E9_FIELDS_TEMPLATE

Info

• result: No Data

Warning

• customfield_10117. The Custom-field  Test must exist on the target instance.

Error

• customfield_10115. The Custom-field doesn't exist.

AO_D195E9_CUSTOM_MAIL_TEMPLATE

Info

• result: No Data

Warning

• BODY_SECTION: [Source Workflow Status]. The Status To Do must exist on the target instance.
• Project_Id: 10005. Project Demo Project must exist on the target instance.
• SUBJECT: [Source Workflow Status]. The Status To Do must exist on the target instance.

Error

• Project_Id: 10005.The Project doesn't exist.

AO_D195E9_ICON

Info

• result: OK

AO_D195E9_CONDITIONAL_RULE

Info

• result: No Data

Warning

• USER_EVALUATOR customfield_10131. The custom-field approver must exist on the target instance.
• USER_EVALUATOR JIRAUSER10108. The Username testuser must exist on the target instance.

Error

• USER_EVALUATOR customfield_10131. The Custom-field doesn't exist
• USER_EVALUATOR JIRAUSER10108. The Userkey doesn't exist

AO_D195E9_CONFIG

Info

• result: OK

Warning

• USER_APPROVER_BULK: jirauser10101. Username admintest  must exist on the target instance.
• USER_AWT: jirauser10101. Username admintest  must exist on the target instance.
• USER_COND_RULE: jirauser10101. Username admintest  must exist on the target instance.
• USER_LARGE_BUTTONS: jirauser10101, jirauser10101, jirauser10102. Usernames admintest, demouser, Undefined  must exist on the target instance.
• USER_NOTIFY_NAC: jirauser10101. Username admintest  must exist on the target instance.

Error

• USER_APPROVER_BULK: jirauser10101. The Userkey doesn't exist
• USER_AWT: jirauser10101. The Userkey doesn't exist
• USER_COND_RULE: jirauser10101. The Userkey doesn't exist
• USER_LARGE_BUTTONS: jirauser10102. The Userkey doesn't exist
• USER_NOTIFY_NAC: jirauser10101. The Userkey doesn't exist