Herzum Approval Documentation
Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Overview

The Import Conflicts Analyzer Tab allows to run the analysis of the Jira entities (Projects, Issue Types, workflow statuses, transitions, Users, Groups, Project roles etc) referenced by the file containing the Approval Data that you want to import.

The Import Conflicts Analyzer is able to:

  • validate the required Jira entities (Projects, Issue Types, workflow statuses, transitions, Users, Groups, Project roles etc) used or referenced by the xml files included into the ApprovalDataExport.zip file
  • detect if existing data can have conflicts whit the imported data due to duplication. 

These information allow the Administrator to check if the current Jira instance have the needed entities allowing to achieve a successful import and if any data duplication may occur.

The form allows to select the ApprovalDataExport.zip file to be analyzed, run the Conflicts Analysis and display the result.

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

On clicking Launch, the app identifies, for each Approval table the Jira entities that are referenced by this table.

Import Conflicts Analyze Output

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

The Download Import Conflicts Report button allows to download a file that lists, for each entity, the Import Conflicts result.

The Report will include any message displayed on the form.

Import Conflicts Analyzer messages

By following a dependency analysis there are two types of messages that can be displayed:

  • Info: these messages report information that doesn't require any action by the sys admin.
  • Error: these messages inform about missing Jira entities referenced by the Approval Tables
  • Warning: these messages inform about duplicated configuration

The Errors relating missing Jira entities referenced by the Approval Tables must be fixed before to perform the Approval Data import in order to allow the operation to succeed. 

The Warnings relating duplicated configuration can be fixed after that the import is performed.


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
  • Modified_User: admin. Username admintest exists.

Error

  • Modified_User: admin. Username admin do not exist on this instance.

Warning

  • Language Pack having name Test is duplicated


AO_D195E9_APPROVAL_HISTORY

Info

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

AO_D195E9_NTF_SCHEME_DETAIL

Info

  • result: No Data
  • result: OK
  • NOTIFY_EXPRESSION: <include><users>admin, test</users></include><exclude></exclude>. Usernames admin, test exist.

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 are not included into ApprovalDataExport file

AO_D195E9_APPROVAL_DEFINERS

Info

  • result: No Data

Error

  • Definer: admin; Type:User. Username admin doesn't exist 
  • Definer: Test; Type: Group.  Group Test doesn't exist 
  • Definer: TestR; Type: Role.  Role TestR doesn't exist 
  • Issue Type Demo Test is not associated to  Project Demo Project.
  • Project: Demo Test Project doesn't exist 
  • Issue Type: Demo Test doesn't exist 

AO_D195E9_APPROVAL_DELEGATED

Info

  • result: No Data

Error

  • Delegated key: Username admintest doesn't exist.
  • Delegator key: Username admintest doesn't exist.
  • Issue Type Demo Test is not associated to  Project Demo Project.
  • Project: Demo Test Project doesn't exist 
  • Issue Type: Demo Test doesn't exist 

AO_D195E9_APPROVAL_MENU_PERM

Info

  • result: No Data

Error

  • User: Username admintest doesn't exist 
  • Goup: Group admintest doesn't exist 

AO_D195E9_APPROVAL_MRA

Info

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

Error

  • The Workflow transition Approve is not outgoing from Workflow status To Do.
  • SOURCE_STATUS_ID: The Workflow status To Do doesn't exist
  • TRANSITION_ID:  The Workflow transition Approve doesn't exist

AO_D195E9_APPROVAL_NOT_NOTIFY

Info

  • result: No Data

Error

  • The Custom-field  Approvers doesn't exist.
  • The Username testuser doesn't exist.
  • The Group Gtest doesn't exist.
  • The Project Role Administrators doesn't exist.

AO_D195E9_APPROVAL_PROJECTS

Info

  • result: No Data

Error

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

AO_D195E9_APPROVAL_RECIPIENTS

Info

  • result: No Data

Error

  • The Custom-field  Approvers doesn't exist
  • The Username test.test doesn't exist
  • The Group Gtest  doesn't exist
  • The Project Role Administrators  doesn't exist

AO_D195E9_APPROVAL_REQUESTERS

Info

  • result: No Data

Error

  • The Username test.test doesn't exist
  • The Group Gtest  doesn't exist
  • The Project Role Administrators  doesn't exist
  • Issue Type Demo Test is not associated to  Project Demo Project.
  • Project: Demo Test Project doesn't exist 
  • Issue Type: Demo Test doesn't exist 

AO_D195E9_APPROVAL_SEQUENCE

Info

  • result: No Data

Error

  • The Username test.test doesn't exist


AO_D195E9_AUTO_TRANSITION

Info

  • The AUTO_TRANSITION data will not be imported


AO_D195E9_CONFIG_PROPERTIES

Info

  • result: OK

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

AO_D195E9_APPROVAL_MAPPING

Info

  • result: OK
  • Locked data will not be imported

Error

  • AREA_SERVICE_NAME: ApprovalRequestAutomation. The Service having Name ApprovalRequestAutomation Class com.herzum.approval.service.email.ApprovalRequestAutomation doesn't exist.
  • DA_SERVICE_NAME: ApprovalActionAutomation. The Service having Name ApprovalActionAutomation Class com.herzum.approval.service.email.ApprovalActionAutomation doesn't exist.
  • AREA_DATE_PICKER: The Custom-field  Test  doesn't exist.
  • DA_USER_KEY: The Username testuser  doesn't exist.
  • DESTINATION_STATUS_ID: The Status Done doesn't exist.
  • SOURCE_STATUS_ID: 10005. The Status Waiting Approval doesn't exist.
  • Issue Type Demo Test is not associated to  Project Demo Project.
  • Project: Demo Test Project doesn't exist. 
  • Issue Type: Demo Test doesn't exist.
  • SUPER_APPROVERS_EXPRESSION: <include><users>admin, test</users></include><exclude></exclude>. Usernames admin, test do not exist.
  • TRANSITION_ID: The Workflow Approve transition doesn't exist.
  • TRANSITION_ON_REJECTING: The Workflow Reject transition doesn't exist.
  • the Workflow transition Approve (having as destination status Done) outgoing  from the Status ToDo doesn't exist on the workflow associated to Issue Type Demo Test  Project Demo Project.
  • the Workflow transition Reject outgoing  from the Status ToDo doesn't exist on the workflow associated to Issue Type Demo Test  Project Demo Project.

O_D195E9_APPROVAL

Info

  • result: No Data

Error

  • The Username test.test doesn't exist
  • The Group Gtest  doesn't exist
  • The Project Role Administrators  doesn't exist
  • GROUP_PICKER: the Custom-field  Test doesn't exist.
  • User_Picker: The Custom-field  Test doesn't exist.
  • USER_PICKER_ALL_EXPR: <include><users>admin, test</users></include><exclude></exclude>. Usernames admin, test don't exist.
  • User_Picker_Any: The Custom-field  Test doesn't exist.
  • USER_PICKER_ANY_EXPR: <include><users>admin, test</users></include><exclude></exclude>. Usernames admin, test don't exist.

Warning

  • The Approval having name Test is duplicated

AO_D195E9_FIELDS_TEMPLATE

Info

  • result: No Data

Error

  • The Custom-field  Test doesn't exist.


AO_D195E9_CUSTOM_MAIL_TEMPLATE

Info

  • result: No Data

Error

  • BODY_SECTION: [Source Workflow Status]. The Status To Do doesn't exist.
  • SUBJECT: [Source Workflow Status]. The Status To Do doesn't exist.
  • The Project Demo Project doesn't exist.

AO_D195E9_ICON

Info

  • result: OK

AO_D195E9_CONDITIONAL_RULE

Info

  • result: No Data

Error

  • USER_EVALUATOR: The custom-field approver  doesn't exist
  • USER_EVALUATOR: The Username testuser  doesn't exist

Warning

  • Conditional Rule having name Test is duplicated

AO_D195E9_CONFIG

Info

  • result: OK

Error

  • USER_APPROVER_BULK: jirauser10101. The Username admintest  doesn't exist
  • USER_AWT: The Username admintest doesn't exist
  • USER_COND_RULE: The Username admintest doesn't exist
  • USER_LARGE_BUTTONS: The Username admintest doesn't exist
  • USER_NOTIFY_NAC: The Username admintest doesn't exist
  • No labels