Symptoms

When clicking on the save button on the Herzum Quick Linker Partnership Configuration screen you get a Warning Message:

If you encounter this alert check the following:

• user exists and password is correct
• user applied as Source Credential has the permission to log on the Source JIRA Instance
• user applied as Destination Credential has the permission to log on the Target JIRA Instance
• the JIRA instance on the remote server is reachable by clicking on the Test Connection button
• the Herzum Quick Linker add-on installed on the remote JIRA instance is enabled and licence is valid.
  
  

Herzum Quick Linker Partnership Configuration screen

Symptoms

When clicking on the save button on the Herzum Quick Linker Partnership Configuration screen you get a Warning Message:

If you encounter this alert it's due:

• the JIRA instance on the remote server is not reachable
• the Herzum Quick Linker installed on the JIRA instance that is configured destination URL on the partnership is not valid. It can be caused by one of the followings:
  • the add-on version installed on the remote JIRA Instance is not compatible with the version installed on the Source Instance.
  • the add-on installed on the remote JIRA Instance isn't enabled
  • the add-on has not be installed on the remote JIRA Instance
  • the add-on license is not Valid

Herzum Quick Linker Partnership Configuration screen

Symptoms

When clicking on the Herzum Quick Linker Main Partnership Configuration screen you get a Warning Message:

If you encounter this alert it's due the JIRA instance on the remote server isn't reachable or the provided credentials aren't valid anymore.

If the problem is caused by invalid credentials, you can encounter the following scenarios:

• the inactive partership is turned in red: you can edit it, update the user/password configured as source/destination credential and save.
• the inactive partership is turned in orange: you can edit it but you are allowed to update only the user/password configured as destination credential.

Herzum Quick Linker Main Partnership Configuration screen

Symptoms

When clicking on an Herzum Quick Linker Action button to create and link a new issue you get a Warning Message:

If you encounter this alert it's due invalid credentials allowing issue creation and linking.

In order to fix that follow Recommended best practices for partnership credentials.

HQL Message: Permission Violation

Symptoms

When clicking on the Herzum Quick Linker Main Mapping Configuration screen you get a Warning Message:

If you encounter this alert it's due:

• the partnership is not active
• the configured mapping is no more consistent with data in JIRA cause of:
  • source project key has been updated
  • target project key has been updated
  • source issue type doesn't exist anymore or it isn't still active for the source project
  • destination issue type doesn't exist anymore or it isn't still active for the destination project
  • the selected Issue Link Type has been dropped on the source JIRA instance
  • the Quick Action Button/Post Function has been unchecked and the selected priority has been dropped on the destination JIRA instance

If the problem is due an incosistent Mapping configuration, you can encounter the following scenarios:

• the inactive mapping is turned in red: you can update data and save.
• the inactive mapping is turned in orange: you cannot edit it; the configured mapping can be activated only via the Herzum Quick Linker Mapping Configuration screen of the remote JIRA instance joining the partnership.

Herzum Quick Linker Main Mapping Configuration screen

Symptoms

When clicking on the Herzum Quick Linker Main Mapping Configuration screen you get a Warning Message:

If you encounter this alert it's due:

• all Issue Link Types have been dropped on the source JIRA instance
• issue Linking has been deactivated.

Herzum Quick Linker Main Mapping Configuration screen

Symptoms

When configuring a new Mapping or updating an existing one, on save, you get a Warning Message:

If you encounter this alert it's due:

a mapping has been already configured having same partnership, source project, source issue type and button label.

You must change at least one of the listed parameters and then save.    

Herzum Quick Linker Mapping Configuration screen

Symptoms

When configuring a new Mapping or updating an existing one, on save, you get a Warning Message:

If you encounter this alert it's due:

• you are trying to configure a mapping having as destination issue type a Sub-task issue type and  as target project a project different from the source project: this configuration isn't allowed
• you are trying to configure a mapping having  as destination issue type a Sub-task issue type and partnership is configured toward a remote url: this configuration isn't allowed.

Herzum Quick Linker Mapping Configuration screen

Symptoms 

When configuring the Fields Mappings for a given Mapping, on adding it, you get a Warning Message: 

If you encounter this alert it's due:

• you are trying to configure a field mapping having same source and target fields of an existing one.

Herzum Quick Linker Mapping Configuration screen

Symptoms 

When configuring the Fields Mappings for a given Mapping, on adding it, you get a Warning Message: 

If you encounter this alert it's due you are trying to configure a not allowed field mapping.

Review HQL - Syncing 3.0 Guide for further details on allowed fields mappings.

Herzum Quick Linker Mapping Configuration screen

Symptoms

When transitioning the issue status, you get a Warning Message:

 If you encounter this alert it's due:

• the partnership selected as input for the escalate issue post function configured on the workflow transition is inactive
• at least one mapping configured for the partnership selected as input for the escalate issue post function configured on the workflow transition is inactive

If the problem is due an inactive Partnership you can fix that by accessing to the Herzum Quick Linker Main Partnership Configuration screen and following instructions provided for Partnership Configuration issues.

If the problem is due an inactive Mapping you can fix that by accessing to the Herzum Quick Linker Main Mapping Configuration screen and following instructions provided for Mapping Configuration issues.

Issue screen

Symptoms

When transitioning the issue status, you get a Warning Message:

If you encounter this alert it's due the user configured on the partnership as destination credentials has not the required grants on the target project.

Follow Recommended best practices for Partnership credentials to fix that.

Issue screen

Symptoms

When displaying the post functions configured for a workflow transition, you get the Message:

If you encounter this alert it's due:

the partnership selected as input for the escalate issue post function configured on the workflow transition is inactive.

In order to fix that:

• click on edit, update parameters of the Escalate Issue Function and save.
• access to the Herzum Quick Linker Main Partnership Configuration screen and follow instructions provided for Partnership Configuration issues.

Workflow's transition configuration screen

Symptoms

When clicking on one button on the Quick Actions  panel you get the Message:

If you encounter this alert it's due:

• the configured mapping is inactive
• one or more mappings have been configured toward an partnership that is deactivate.

In order to fix that:

• access to the Herzum Quick Linker Main Mapping Configuration screen and follow instructions provided for Mapping Configuration issues
• access to the Herzum Quick Linker Main Partnership Configuration screen and following instructions provided for Partnership Configuration issues

Issue screen

When displaying the issue the Quick Actions  panel you get the Message:

If you encounter this alert it's due:

• one or more mappings have been configured toward a partnership that has been deactivated.

In order to fix that:

• access to the Herzum Quick Linker Main Partnership Configuration screen and following instructions provided for Partnership Configuration issues

Issue screen

When displaying the Quick Links on the Herzum Quick Links panel you get the Message: Issue Link not available.

If you encounter this alert it's due:

• the current issue has been linked via a remote mapping that has been configured toward a partnership that is deactivate.

In order to fix that:

• contact the JIRA Administrators of the remote JIRA instance asking to activate the partnership.

Herzum Quick Links panel 

When displaying the Quick Links on the Herzum Quick Links panel you get the Message: Missing Link type.

If you encounter this alert it's due the issue link type has been deleted.

Herzum Quick Links panel 

When clicking on the Button to create and linking a new issue you get the Message:

If you encounter this alert it's due the user configured  as destination credentials on the partnership has not the required grants on the target project.

Follow Recommended best practices for Partnership credentials to fix that.

Issue screen

When clicking on the Button to link an existing issue you get the Message:

If you encounter this alert it's due the user configured on the partnership as destination credentials has not the required grants on the target project.

Follow Recommended best practices for Partnership credentials to fix that.

Issue screen

When clicking on the Button to create and linking a new issue you get the Message:

If you encounter this alert it's due the user configured on the partnership as destination credentials has not the required grants on the target project.

Follow Recommended best practices for Partnership credentials to fix that.

Issue screen

When clicking on the Button to link an existing issue you get the Message:

If you encounter this alert it's due the user configured on the partnership as destination credentials has not the required grants on the target project.

Follow Recommended best practices for Partnership credentials to fix that.

Issue screen

When editing Affect/Fix Version/s, Component/s, Assignee, Reporter, Priority, Custom fields, Summary or Description, on the issue Edit Screen, a new Comment is added as reported bellow:

If you encounter this alert it's due the user configured  as destination credentials on the partnership has not the required grants on the target project.

Follow Recommended best practices for Partnership credentials

Issue screen

When editing the Fix Version, on the issue Edit Screen, a new Comment is added as reported bellow:

If you encounter this alert it's due the user configured on the partnership as destination credentials has not the required grants on the target project.

Follow Recommended best practices for Partnership credentials

Issue screen

When editing the Assigee, on the issue Edit Screen, a new Comment is added as reported bellow:

HQL sync field error message 

If you encounter this alert it's due the user configured on the partnership as destination credentials has not the required grants on the target project.

Follow Recommended best practices for Partnership credentials

Issue screen

When adding an Attachment, on the issue Edit Screen, a new Comment is added as reported bellow:

If you encounter this alert it's due the user configured on the partnership as destination credentials has not the required grants on the target project.

Follow Recommended best practices for Partnership credentials

Issue screen

When editing the Reporter, on the issue Edit Screen, a new Comment is added as reported bellow:

If you encounter this alert it's due the user configured on the partnership as destination credentials has not the required grants on the target project.

Follow Recommended best practices for Partnership credentials.

Issue screen

The following Comment is displayed:

If you encounter this alert it's due the user configured on the partnership as destination credentials has not the required grants on the target project.

Follow Recommended best practices for Partnership credentials.

Issue screen

When deleting a Comment, a new Comment is added as reported bellow:

If you encounter this alert it's due the user configured on the partnership as destination credentials has not the required grants on the target project.

Follow Recommended best practices for Partnership credentials.

Issue screen

When editing a Comment, a new Comment is added as reported bellow:

If you encounter this alert it's due the user configured on the partnership as destination credentials has not the required grants on the target project.

Follow Recommended best practices for Partnership credentials.

Issue screen

When editing the Affects/Fix Version/s, Component/s, Assignee, Reporter or Priority on the issue Edit Screen, a new Comment is added on the Source and on the Target Issue as reported bellow:

If you encounter this alert it's due selected Affects/Fix Version/s, Component/s, Assignee, Reporter or Priority are not admissible for the Target Project.

Align Affects/Fix Version/s, Component/s, Assignee, Reporter, Priority on Source/Target Project/JIRA instance to allow synchronization.

Issue screen

When editing the issue a new Comment is added on the Source and on the Target Issue as reported bellow:

If you encounter this alert it's due the target issue isn't editable (e.g. issue status is 'Closed').

Issue screen