I found another discussion that mentioned several ways to mention one issue from another, but none are working for me. Here's what I've tried:
I do not prefer to do the following as it's time consuming:
Thanks for your help.
Jira Cloud changed a lot since this question was created, so I would like to update this thread to add the current behavior when adding a link to another issue on the description and comments.
The new issue view uses Markdown editor and in order to mention another ticket, you can simply type the issue key and press space or enter/return for the text to be updated with the link. You can also paste the link to the description or comment that will automatically be converted to the link showing the issue type, issue key, summary, and status.
If you are still using the old view that uses Wiki Markup, then it's necessary to type the issue key and save the comment/description for it to show the issue type, issue key, and status or use [IT-123|https://xxxxxx.atlassian.net/browse/IT-123].
Hope this clarifies!
If you have any other questions or if you are facing issues, since the original question is from 2018, please, raise a new question so we can better investigate what is happening.
I am glad that typing the issue key in the new Markdown editor creates a link. However, it only works if you type in upper case. IT-123 will convert; it-123 will not. It's a minor annoyance, but in the old Markup editor, either case will be converted into a link to the referenced issue.
Also, the new Markdown editor only seems to be available when viewing an issue. Creating a new issue and transitioning an issue through the workflow still use the old Markup editor. A bigger annoyance in that issue keys that appear as links in the old Markup editor do not become links in the new Markdown view. It is a shame that the new view is not backwards compatible.
Hello @Michael Simmons,
Thank you for reaching out to Community!
When we need to mention a ticket on a comment, it’s necessary to type the issue key and press space or enter. If we just type and save the comment, it won’t convert the issue key to a link.
Also, when the ticket doesn’t exist, it will show only plain text.
I don't think any of those work for you, there are only 2 ways that worked for me, and both related to actual links.
I put all my attempts in the video in case someone will find it easier that way to learn (there are no ads or anything) : https://www.youtube.com/watch?v=USj7HKy1u6w
I came across this problem as well, I found that it is more than just typing the ticket ID, you actually have to press return right after you type it so it triggers a ticket link. If the link doesn't appear as soon as you press return, then it won't just magically appear after you submit the comment.
Well, that works, but it's not as nice as the old view which automatically translated Jira issue numbers into links. Doing it this way, the issue number, summary, and status all appear in the text. If I switch to the old issue view, I only have to enter the issue number and save and the wiki markup editor converts it to an issue link with just the number and status, and when you mouse-over the link you can see the summary.
In the new editor, if after pressing enter to get the issue link you then edit the link to remove the summary, it treats it as an external link; that is, you don't get the status or the summary on mouse-over.
Leave it to Atlassian to take 1 step forward and two back on the UI.
But, if you enter it via the old view, you only get the issue link IN THE OLD VIEW! The new view shows the issue number as text without a link or status. So it appears to be an issue with the new page renderer not recognizing the issue number and creating the link.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events