Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Below you can find some potential issues that you may be running into, as well as the way to fix them.

Table of Contents

  

Anchor
PC
PC
Partnership Configuration issues

Symptoms

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

Warning
iconfalse

"Source URL" must be this instance's Base URL.

If you encounter this alert, check the Source instance Base URL on

  • System→ General configuration->Base URL
  • Case of HTTPS URL, the connector directive in the Tomcat server.xml file:

Symptoms

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

Warning
iconfalse

Destination URL is invalid.

If you encounter this alert, check the Destination instance Base URL on

  • System→ General configuration->Base URL
  • Connector directive in the Tomcat server.xml file:
    • proxyName

    • scheme

Symptoms

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

Warning
iconfalse

Failure authenticating with Source Username when calling source URL from source URL 

If you encounter this alert, check the Source Username exists, it is active, it is a JIRA Jira user and password is correct.

Symptoms

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

Warning
iconfalse

Failure authenticating with Destination Username when calling destination URL from source URL


If you encounter this alert, check the Destination Username exists, it is active, it is a JIRA Jira user and password is correct

Symptoms

When editing the Destination URL in the Partnership Configuration screen you get a Warning Message:

Warning
iconfalse

Destination URL is inconsistent with old instance.

If you encounter this alert, you are trying to perform an illegal action:

it's not allowed to transform an existing local partnership into a remote partnership.

Symptoms

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

Warning
iconfalse

Some partnerships are inactive (the inactive partnerships are displayed in red/orange text). It could depend on temporary connection troubles or setting parameters inconsistencies.


 

If you encounter this alert it's due the JIRA 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:

Warning
iconfalse
titleHQL Message: Permission Violation

Creation permission has not been provided for the target Project.

If you think this message is wrong, please contact your JIRA administrators


 

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

Anchor
MC
MC
Mapping Configuration issues

Symptoms

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

Warning
iconfalse

Some mappings are inactive (the inactive mappings are displayed in red/orange text). It could depend on Partnership inactivation or setting parameters inconsistencies. Please, update setting parameters to enable them.


 

If you encounter this alert it's due:

  • the partnership is not active
  • the configured mapping is no more consistent with data in JIRA 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
    • has been dropped on the source JIRA 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 theremote JIRA 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:

Warning
iconfalse

Any link can be created. Issue linking is deactivate or not exist any.


 

If you encounter this alert it's due:

  • have been dropped on the source JIRA 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:

Warning
iconfalse

Duplicated value. Change the Button Label.


 

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:

Warning
iconfalse

Mapping can't be created. If destination issue type is a sub task Source Project must correspond to Destination Project.


 

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: 

Warning
iconfalse

A fields mapping for selected fields exists already.


 

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: 

Warning
iconfalse

Fields mapping is inconsistent.


 

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

Escalate Post function issues

Symptoms

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

Warning
iconfalse
titleWorkflow Error

Quick Linker Alert: Escalating issue failure. Required action can't be executed cause wrong Mapping Configuration

It seems that you have tried to perform an illegal workflow operation.                   

If you think this message is wrong, please contact your JIRA Jira administrators.


 

 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:

Warning
iconfalse
titleWorkflow Error

Quick Linker Alert: You don't have any or some of the required permissions allowing to escalate issue.

It seems that you have tried to perform an illegal workflow operation.

If you think this message is wrong, please contact your JIRA Jira administrators.


 

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:

Info
iconfalse

Herzum - Quick Linker Plugin - Escalate Issue Configuration:  No associated Partnership.


 

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

Quick Actions Issues

Symptoms

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

Warning
iconfalse
titleHQL Message: Partnership or Mapping Disabled

To enable it, please check Herzum Quick Linker Partnership or Mapping Configuration


 

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:

Issue screen

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

Warning
iconfalse

Some partnerships are inactive. To enable them, please check setting parameters on Herzum Quick Linker Partnership Configuration


 

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:


 


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 Jira Administrators of the remote JIRA 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.

 


Warning

In order to fix that review HQL - Database Documentation 3.0 asking to the Database Administrator to fix that.

Herzum Quick Links panel 

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

Warning
iconfalse

Creation permission has not been provided for the target Project.

 If you think this message is wrong, please contact your JIRA Jira Administrators



 

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:

Warning
iconfalse

Browsing permission has not been provided for target Project.

If you think this message is wrong, please contact your JIRA administrators



 

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:

Warning
iconfalse

Linking permission has not been provided for source or target Project.

If you think this message is wrong, please contact your JIRA administrators


 

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:

Warning
iconfalse

Linking permission has not been provided for source or target Project.

If you think this message is wrong, please contact your JIRA administrators


 

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:

Info
iconfalse
titleUser added a comment - day H:MM AM/PM

HQL sync field error message
Field synchronization can't be performed: user in partnership hasn't "Edit Issue" permission. Issue Hyperlink


 

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:

Info
iconfalse
titleUser added a comment - day H:MM AM/PM

HQL sync field error message
Fix Version/s synchronization can't be performed: user in partnership hasn't "Resolve Issues" permission. Issue Hyperlink


 

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 

Info
iconfalse
titleUser added a comment - day H:MM AM/PM

 Assignee synchronization can't be performed: user in partnership hasn't "Assign Issues" permission. Issue Hyperlink


 

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:

Info
iconfalse
titleUser added a comment - day H:MM AM/PM

HQL sync field error message

Attachment synchronization can't be performed: user in partnership hasn't "Create Attachment" permission. Issue Hyperlink


 

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:

Info
iconfalse
titleUser added a comment - day H:MM AM/PM

Reporter synchronization can't be performed: user in partnership hasn't "Modify Reporter " permission. Issue Hyperlink


 

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:

Info
iconfalse
titleUser added a comment - day H:MM AM/PM

Add Comment synchronization can't be performed: user in partnership hasn't "Add Comments" permission. Issue Hyperlink


 

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:

Info
iconfalse
titleUser added a comment - day H:MM AM/PM

Delete Comment synchronization can't be performed: user in partnership hasn't "Edit Comments" permission. Issue Hyperlink

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:

Info
iconfalse
titleUser added a comment - day H:MM AM/PM

Edit Comment synchronization can't be performed: user in partnership hasn't "Edit Comments" permission. Issue Hyperlink

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:

Info
iconfalse
titleUser added a comment - day H:MM AM/PM

HQL sync field error message 

Affects/Fix Version/s/Component/s/Priority/Assignee/Reporter: List of selected Affects/Fix Version/s  not exist on target. Issue Hyperlink


 

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:

Info
iconfalse
titleUser added a comment - day H:MM AM/PM

HQL sync field error message 

Field 1: "Field Value" .....Field n: "Field Value" can not be synchronized. Issue Hyperlink


 

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


Issue screen