-
Suggestion
-
Resolution: Unresolved
-
44
-
21
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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.
- is related to
-
- Gathering Interest
-
- Gathering Interest
-
- Gathering Interest
[JRACLOUD-37224] Allow disabling of issue key links
This would be helpful if it can be customized by project type or even project. This feature is nice in the Jira Software projects. However, for Jira Service projects, since the description may populate from an email, we have instances where part numbers are being turned into a Jira hyperlink incorrectly.
Hey 222231af5fc9 thank you for sharing this image:
You may be interested in voting for this issue too: JRACLOUD-76100 – Improve smart links - add further display options to link preferences
this auto-linking will also eat text that's inside code snippets like `this is a bunch of text for JIRACLOUD-37224` would change JIRACLOUD-37224 into that silly titled link thing.
We are moving from Jira server to Jira Cloud and agree the ability to customise the display of the issue keys would be of benefit: to turn links on or off, and choose how much or little data is shown in there.
Until now, while using Jira Server, we have found the display of issue keys with links is useful - but the display of extra elements in Jira Cloud does clutter up the texts in Descriptions, Comments, etc, as pointed out well by Ryan.
Completely agree with Ryan.
I have started to build Automation into our 'soon to be' use of JSM.
Our automation will be posting comments to JSM and Jira issues using smart values (specifically issue.key).
The inclusion of a dynamic issue link, which includes the issue status, means that over time the comment bears no relevance to the linked issue status as it will change, making the comment audit trail at the very least misleading.
Ever since we moved from Jira Server to Jira Cloud, this was one of the first features that I noticed that I immediately disliked. The main part of it that troubles us is the inclusion of the Summary. Often times, my team and I will reference other issues like this (trying to translate what I see visually since I can't attach a screenshot):
The issue described in [ [?] PSA-1845: QA: Cannot add EFT during Setup for Recurring Payments OPEN ] is similar to [ [*] PSA-1425: Unable to setup EFT using ACH CLOSED ]; however, the issue may have been reintroduced by [ [*]
API-162: EFT gets stuck after attempting to change payment type CLOSED ] or [ [*] API-163: CyberSource ERROR responses not being handled correctly CLOSED ].
I'm not sure why more people aren't complaining about this, but that is extremely difficult to parse and read! The important details get lost in all that mess, and this is just one example of it.
We don't necessarily need the ability to disable the feature, but the ability to customize what appears in the auto-link. I see value with the link containing the following:
- Issue Type icon
- Issue Key
- Status
But including the Summary just adds unnecessary noise! I know we can reformat the links, but that takes more work that necessary. If anything, the default should be to exclude the Summary, and allow people to reformat the link to include it if they want to.
EDIT: I just uploaded an image just in case you needed to see an actual visual on how terrible this is:
https://drive.google.com/file/d/1tuJjSQ2xiD5u3AG73OFR_IN2u-7vAjcP/view?usp=sharing
We use SERVER, but that ticket has been denied. Grr...
Similar to a <nowiki> tag or something. We work on multiple networks, and old tickets are being linked on our older network. It's annoying at the very least.
Would be a helpful feature to have an option to segregate, if a hyperlink or pure literals of the issue will be send!
Yesterday we also had a usercase where the first part of the ZIPCODE (3 first digits) was translated to a Jira Issue - LOL
Not good for agents or customers.
The reason few customers experience this is because this isn't a big issue for small companies, but when working with big companies around the globe - something similar to this really causing an impact, making them select other tools.
Created 10 years ago and still not addressed. This is needed so that the external portal is more useful and escalating files to different groups does not get cluttered. If we name the file after the ticket (as we often do for tracking purposes) then it turns into a link since it is just updating that string of text. This makes the escalation notes difficult to read.
I will highlight and link when I need it, else leave the text alone.