-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
None
-
6
-
2
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Currently in JIRA, if issue keys are inputted into a field (description, comment, etc), it will automatically be turned into a link to that issue.
This is convenient, but at the same time, if the issue is exported (or if the value is being extracted via API), the value of that field that is obtained contains hyperlinks :
<customfield id="customfield_10407" key="com.pyxis.greenhopper.jira:gh-epic-label"> <customfieldname>Epic Name</customfieldname> <customfieldvalues> <customfieldvalue> <a href="http://10.60.2.150/jira61/browse/PNS-5" title="EPIC TEST" class="issue-link" data-issue-key="PNS-5">PNS-5</a> </customfieldvalue> </customfieldvalues> </customfield>
As such, having the option to disable this functionality that automatically changes issue keys into links could be rather useful as well.
- relates to
-
- Gathering Interest
[JRASERVER-37224] Allow disabling of issue key links
This is dumb. We store files on the network with folder names that match the key. For example, c:\Folders\20240207_SD-1794 and when that path is put into a comment, Jira adds a link automatically to the SD-1794 text part. How is that useful? When the ticket is resolved, the customer gets that path name with a strikethru line where the SD-1794 is because it has been resolved. It just looks bad and provides no use at all.
Nooooooo!!! Govt works across multiple networks and uses the same project codes for each network, so our more mature Jira instance is always trying to link to old tickets that aren't related. It's annoying, to say the least. Surely this can be implemented for both JRASERVER and JRACLOUD?
Hi,
Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.
For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.
Thanks again.
Regards,
Jira Product Management
We would need the option to disable it selectively for certain fields. The vast majority of the time, this feature is extremely useful, but sometimes, if a value is in a custom field, e.g., storing an external ID that happens to have a similar pattern, it is very confusing.