General troubleshooting guidelines
Below you can find some potential issues that you may be running into, as well as the way to fix them.
Symptoms
When clicking on the save button on the Herzum Quick Linker Partnership Configuration screen you get a Warning Message:
"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:
proxyName
scheme
Symptoms
When clicking on the save button on the Herzum Quick Linker Partnership Configuration screen you get a Warning Message:
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:
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 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:
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 user and password is correct
Symptoms
When editing the Destination URL in the Partnership Configuration screen you get a Warning Message:
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:
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 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:
HQL 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
Symptoms
When clicking on the Herzum Quick Linker Main Mapping Configuration screen you get a Warning Message:
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 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