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 | ||||
|---|---|---|---|---|
|
Symptoms
When clicking on the save button on the Herzum Quick Linker Partnership Configuration screen you get a Warning Message:
| Warning | ||
|---|---|---|
| ||
You cannot perform this action. The remote server is not reachable or user is invalid. Please try later. |
"Source URL" must be this instance's Base URL. |
If you encounter this alert, check the following:
Herzum Quick Linker Partnership Configuration screen
Source instance Base URL on
- System→ General configuration->Base URL
- Case of HTTPS URL, the connector directive in the Tomcat server.xml file:
proxyName
Info The proxyName parameter should be set to the FQDN that the application server will be accessed on - for example jira.example.com if accessing it on http://jira.example.com or example.com if accessing it on http://www.example.com/jira. It should not include the context path.
scheme
Info E.g. scheme="https" secure="true"
Symptoms
When clicking on the save button on the Herzum Quick Linker Partnership Configuration screen you get a Warning Message:
| Warning | ||
|---|---|---|
| ||
You cannot perform this action. The remote server is not reachable or the remote instance has not a valiid Herzum Quick Linker installation. |
Destination URL is invalid. |
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
, 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 | ||
|---|---|---|
| ||
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 Main Partnership Configuration screen you get a Warning Message:
| Warning | ||
|---|---|---|
| ||
Some partnerships are inactive (the inactive partnerships are displayed in red/orange text). It could depend on temporary connection troubles or setting parameters inconsistencies. |
Warning Message:
| Warning | ||
|---|---|---|
| ||
Failure authenticating with Destination Username when calling destination URL from source URL |
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.
, 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:
| Warning | ||
|---|---|---|
| ||
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 an the Herzum Quick Linker Action button to create and link a new issue Main Partnership Configuration screen you get a Warning Message:
| Warning | ||||
|---|---|---|---|---|
| ||||
Creation permission has not been provided for the target Project. If you think this message is wrong, please contact your JIRA administrators |
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 invalid credentials allowing issue creation and linking.
In order to fix that follow /wiki/spaces/HQL/pages/311922007.
HQL Message: Permission Violation
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 the an Herzum Quick Linker Main Mapping Configuration screen Action button to create and link a new issue you get a Warning Message:
| Warning | ||
|---|---|---|
| ||
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
- has been dropped on the source JIRA instance
If the problem is due an incosistent Mapping configuration, you can encounter the following scenarios:
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 | ||
|---|---|---|
| ||
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 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 | ||
|---|---|---|
| ||
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, :
| Warning | ||||
|---|---|---|---|---|
| ||||
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 /wiki/spaces/HQL/pages/311922007.
HQL Message: Permission Violation
| Anchor | ||||
|---|---|---|---|---|
|
Symptoms
When clicking on the Herzum Quick Linker Main Mapping Configuration screen you get a Warning Message:
| Warning | ||
|---|---|---|
| ||
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
- has been dropped on the source 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 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 | ||
|---|---|---|
| ||
Mapping Any link can 't be created. If destination issue type is a sub task Source Project must correspond to Destination Project. |
Issue linking is deactivate or not exist any. |
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.
- have been dropped on the source Jira instance
- issue Linking has been deactivated.
Herzum Quick Linker Main Mapping Configuration screen
Symptoms
When configuring the Fields Mappings for a given Mapping, on adding it, you a new Mapping or updating an existing one, on save, you get a Warning Message:
| Warning | ||
|---|---|---|
| ||
A fields mapping for selected fields exists already. |
Duplicated value. Change the Button Label. |
If you encounter this alert it's due:
you are trying to configure a field mappinga mapping has been already configured having same partnership, source
and target fields of an existing one.
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 the Fields Mappings for a given Mapping, on adding ita new Mapping or updating an existing one, on save, you get a Warning Message:
| Warning | ||
|---|---|---|
| ||
Fields mapping is inconsistent. |
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 due:
- you are trying to configure
Review HQL - Syncing 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 | ||||
|---|---|---|---|---|
| ||||
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 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 | ||||
|---|---|---|---|---|
| ||||
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 administrators. |
- 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 | ||
|---|---|---|
| ||
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 | ||
|---|---|---|
| ||
Fields mapping is inconsistent. |
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 due you are trying to configure a not allowed field mapping.
Review /wiki/spaces/HQL/pages/311922007 to fix that313395897 Guide for further details on allowed fields mappings.
Herzum Quick Linker Mapping Configuration screen
Escalate Post function issues
Symptoms
When displaying the post functions configured for a workflow transition, you get the transitioning the issue status, you get a Warning Message:
| Infowarning | ||||
|---|---|---|---|---|
| ||||
Herzum - Quick Linker Plugin - Escalate Issue Configuration: No associated Partnership. |
If
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 administrators. |
If you encounter this alert it's due: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
In order to fix that:
- click on edit, update parameters of the Escalate Issue Function and save.
- access to
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
PartnershipMapping Configuration screen and
followfollowing instructions provided for
Partnership
Workflow's transition configuration screen
Quick Actions Issues
Symptoms
When clicking on one button on the Quick Actions panel you get the
Issue screen
Symptoms
When transitioning the issue status, you get a Warning Message:
| Warning | ||||
|---|---|---|---|---|
| ||||
To enable it, please check Herzum Quick Linker Partnership or Mapping Configuration |
| |||
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 administrators. |
When displaying the issue the Quick Actions panel you get the Message:
| Warning | ||
|---|---|---|
| ||
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 :
- 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
the user configured on the partnership as destination credentials has not the required grants on the target project.
Follow /wiki/spaces/HQL/pages/311922007 to fix that.
Issue screen
Symptoms
When displaying the post functions configured for a workflow transition, you get the Message:
| Info | ||
|---|---|---|
| ||
Herzum - Quick Linker Plugin - Escalate Issue Configuration: No associated Partnership. |
If you encounter this alert it's due:
one or more mappings have been configured toward a partnership that has been deactivatedthe 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
Issue screen
- .
Workflow's transition configuration screen
Quick Actions Issues
Symptoms
When clicking on one button on the Quick Actions panel you get the Message: Issue Link not available.
| Warning | ||||
|---|---|---|---|---|
| ||||
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:
- only the JIRA Administrators of the remote JIRA instance is allowed 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.
- 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:
| Warning | ||
|---|---|---|
| ||
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 the issue link type has been deleted.
due:
- one or more mappings have been configured toward a partnership that has been deactivated.
In order
to fix that review /wiki/spaces/HQL/pages/316837684 asking to the Database Administrator to fix that.
Herzum Quick Links panel
When clicking on the Button to create and linking a new issue 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:
| icon | false |
|---|
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 the user configured on the partnership as destination credentials has not the required grants on the target project.
Follow /wiki/spaces/HQL/pages/311922007 to fix that.
Issue screen
When clicking on the Button to link an existing issue you get the Message:
| icon | false |
|---|
Browsing permission has not been provided for target Project.
If you think this message is wrong, please contact your JIRA administrators
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 user configured on the partnership as destination credentials has not the required grants on the target project.Follow s due the issue link type has been deleted.
| Warning |
|---|
In order to fix that review /wiki/spaces/HQL/pages/ |
312673710 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 | ||
|---|---|---|
| ||
Linking Creation permission has not been provided for source or the target Project. If you think this message is wrong, please contact your JIRA administrators |
Jira Administrators |
If you encounter this alert it's due the user configured on the partnership as destination credentials as destination credentials on the partnership has not the required grants on the target project.
Follow /wiki/spaces/HQL/pages/311922007 to fix that.
Issue screen
When clicking on the Button to link an existing issue you get the Message:
| Warning | ||
|---|---|---|
| ||
Linking Browsing permission has not been provided for source or target Project. If you think this message is wrong, please contact your 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 /wiki/spaces/HQL/pages/311922007 to fix that.
Issue screen
When editing Affect Ver., Custom fields, Summary or Description, on the issue Edit Screen, a new Comment is added as reported bellow:
| Info | ||||
|---|---|---|---|---|
| ||||
HQL sync field error message |
When clicking on the Button to create and linking a new issue you get the Message:
| Warning | ||
|---|---|---|
| ||
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 /wiki/spaces/HQL/pages/311922007
to fix that.
Issue screen
When editing the Fix Version, on the issue Edit Screen, a new Comment is added as reported bellow:
| Info | ||||
|---|---|---|---|---|
| ||||
HQL sync field error message |
When clicking on the Button to link an existing issue you get the Message:
| Warning | ||
|---|---|---|
| ||
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.
Issue screen
When editing the Assigee/311922007 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 a new Comment is added as reported bellow:HQL sync field error message
| Info | ||||
|---|---|---|---|---|
| ||||
Assignee HQL sync field error message |
Issue Hyperlink |
If you encounter this alert it's due the user configured on as destination credentials on the partnership as destination credentials has not the required grants on the target project.
Follow /wiki/spaces/HQL/pages/311922007
Issue screen
When adding an AttachmentWhen editing the Fix Version, on the issue Edit Screen, a new Comment is added as reported bellow:
| Info | ||||
|---|---|---|---|---|
| ||||
HQL sync field error message |
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.
Issue screen
When editing the ReporterAssigee, on the issue Edit Screen, a new Comment is added as reported bellow:
HQL sync field error message
| Info | ||||
|---|---|---|---|---|
| ||||
Reporter Assignee synchronization can't be performed: user in partnership hasn't "Modify Reporter 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 /wiki/spaces/HQL/pages/311922007.
Issue screen
The following When adding an Attachment, on the issue Edit Screen, a new Comment is added by the systemas reported bellow:
| Info | ||||||
|---|---|---|---|---|---|---|
| Add Comment ||||||
HQL sync field error message Attachment synchronization can't be performed: user in partnership hasn't "Add Comments" permission. Issue Hyperlink |
If you encounter this alert it's due:
Create Attachment" permission. Issue Hyperlink |
If you encounter this alert it's due the user configured on the
Partnershippartnership as destination
credential.If you encounter this alert follow credentials has not the required grants on the target project.
Follow /wiki/spaces/HQL/pages/311922007 to fix that.
Issue screen
When editing the Affects/Fix Version/sReporter, on the issue Edit Screen, a new Comment is added on the Source and on the Target Issue as reported bellow:
| Info | ||||
|---|---|---|---|---|
| ||||
HQL sync field error message Affects/Fix Version/s: List of selected Affects/Fix Version/s doesn't found for synchronization. |
Reporter synchronization can't be performed: user in partnership hasn't "Modify Reporter " permission. Issue Hyperlink |
If you encounter this alert it's due selected Affects/Fix Version/s are not admissible for the Target Project.
Align Version/s for Source/Target Project to allow Version/s syncing to work properly.
Issue screen
When editing the Component/s, on the issue Edit Screen, a new Comment is added on the Source and on the Target Issue as reported bellowthe user configured on the partnership as destination credentials has not the required grants on the target project.
Follow /wiki/spaces/HQL/pages/311922007.
Issue screen
The following Comment is displayed:
| Info | ||||
|---|---|---|---|---|
| ||||
HQL sync field error message Component/s: "List of selected Component/s" doesn't found for synchronization. |
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 selected Component/s are not admissible for the Target Project.
Align Component/s for Source/Target Project to allow Component/s syncing to work properly.
Issue screen
When editing the Priority, on the issue Edit Screen, a new Comment is added on the Source and on the Target Issue user configured on the partnership as destination credentials has not the required grants on the target project.
Follow /wiki/spaces/HQL/pages/311922007.
Issue screen
When deleting a Comment, a new Comment is added as reported bellow:
| Info | ||||
|---|---|---|---|---|
| ||||
HQL sync field error message Priority: "Selected Priority" doesn't found for synchronization. |
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 selected Priority is not admissible for the Target JIRA instance.
Align Priority/ies configured on the Source/Target JIRA instances to allow Priority/ies syncing to work properly.
the user configured on the partnership as destination credentials has not the required grants on the target project.
Follow /wiki/spaces/HQL/pages/311922007.
Issue screen
When editing the Assignee on the issue Edit Screen, a a Comment, a new Comment is added on the Source and on the Target Issue as reported bellow:
| Info | ||||
|---|---|---|---|---|
| ||||
HQL sync field error message Assignee: "Selected Assignee" doesn't found for synchronization. |
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 selected Assignee is not admissible for the Target Project/JIRA Instance.
Align admissible Assignee on the Source/Target Projects/JIRA instances to allow Assignee syncing to work properly.
Issue screen
When editing the Reporter the user configured on the partnership as destination credentials has not the required grants on the target project.
Follow /wiki/spaces/HQL/pages/311922007.
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 | ||||
|---|---|---|---|---|
| ||||
HQL sync field error message Reporter: "Selected Reporter" doesn't found for synchronization. |
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 the selected Reporter is selected Affects/Fix Version/s, Component/s, Assignee, Reporter or Priority are not admissible for the Target Project/JIRA Instance.
Align admissible Reporter on the Source/Target Projects/JIRA instances to allow Reporter syncing to work properly.
.
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 | ||||
|---|---|---|---|---|
| ||||
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