In my previous company just typing the issue code into the comment created a shortcut with summary on hover, and also automatically created an issue link. This saved A LOT of time. I'm an admin on the jira instance in a new company and I don't see a way to set this up - was it broken with an update or something?
A plugin or a way to configure the desired behaviour would be great. Manually making a link is not a nice answer to this question.
I have the same experience as Chris.
I work in two different Jira instances - one from my own company and one from a customers company.
In my companys Jira I can write issue number i.e. "ABC-123" and I get a link to the issue and shows a status. See image below:
I my customers Jira I get nothing of this.
I understand this is settings or a plug-in. Can someone help me how to set ut this in my customers Jira?
I would also like to know why this is not working for us.
We have confirmed the render type is wiki style, but typing ABC-123 or [ABC-123] does not create a link to an issue in a comment field, or an issue description field.
Previously at another clients jira, also in the cloud we were able to link to issues in comments.
Whats up here - is there anything we need to do to make this work or is it an issue with the renderer?
If I switch to the old issue view (append '?oldIssueView=true' to the issue URL), then ticket IDs (ex: SM-70) in the issue description & comments are automatically converted to fancy links () ... but the (getting old) new view just leaves ticket IDs as plain text. Is not auto-linking tickets one of the "features" of the "new" view?
I have exactly the same experience as Kory - If I mention an issue key in a comment or description in old view it will automatically link it beautifully with the ticket summary. If I revert to new view, the link even stays in that useful form.
But if I try to add an issue key in a description or comment in new view, it doesn't automatically link. Square brackets don't seem to have any effect - they just render as square brackets.
I have checked my project settings and both fields are set to Wiki Style Renderer as specified.
It would be helpful to get a straight answer: is the automatic issue linking broken in new view? If so, I can steer those of my colleagues who are (understandably) big fans of auto-linking back to old view.
Frustrating this doesn't work anymore. Used to use this all the time, will switch back to old view as others have done. Would really like to just continue using new view though and be able to use this feature. Quickly linking other issues is a preference though over new view.
Mentioning Jira issues does work already, it just is a bit buggy!
All you have to do is put the Ticket ID like TML-384 in the description or comment field, followed by a white space. The white space or line break is necessary, otherwise it does not work.
Also, please note that the ticket ID has to be written with a normal dash (minus sign), sometimes Jira also uses some special dash, so if conversion does nto work please also try typing the same ID manually.
With those easy rulse it works for me all the time.
This should be the accepted/top answer. All the others suggesting adding a hard link are just wrong. That will fix the issue, but it's not the correct way to do this. E.g. if you rename a project or move to a new domain, etc. then all those hard-links will be broken.
You should be able to do it by pasting the issue URL on the ticket or by mentioning the ticket key, for example:
Let's say the issue key is JSP-0001 and the URL is http://mycompany.atlassian.net/browse/JSP-0001
In this case you should be able to mention the ticket by pasting the whole URL of the ticket or by mentioning only the ticket key, so JIRA will understand the mention and create the link to the other issue.
Let me know if that doesn't work for you, Davide.
I hope it helps
Thanks Eduardo, but copy and pasting full URL's is surely a work around and not a fix to functionality that worked in the old view and no longer works in the new view?
is there a new view roadmap (similar to the nextgen roadmap) that you could like this ticket to so Users can see when it is likely we will get the same level of tagging?
I've tried adding "[key-num]" as well as "[full url]" link styles to my JIRA issue comments, and am not having any luck getting nice looking issue summaries inline. It's just creating plain old links for me. I've read this thread and there doesn't appear to be a complete answer to the question of how this is set up in a cloud-based JIRA account. It certainly isn't working for me in our default config... Thanks,
Can confirm this is broken on a cloud server. I can actually see the page render a link as it loads and then remove it. So close yet so far away...
Here's a movie of it happening:
I figured out that if I open an issue in its own tab it works when I type the issuecode inside square brackets into a comment. This doesn't work if I have an issue open in backlog view and try to comment in there. This is with the wiki renderer turned on for comments.
What I saw in another installation before, was that you could achieve this without the square brackets and in all comments no matter what the view. How might that be done do you know ?
Sorry to bump up an old topic, but this is still the case!
I want to use automation to add the portal link of a service desk issue to a related jira software issue.
But when using issue.url, this "zero-width non-joiner" character between the project key and dash makes the url not usable.
got the same problem. I used the URL in the description and it showed me the status of the ticket. But since yesterday, those links don't work anymore and given as simple link to the ticket without status information. Does anybody had similar problem recently?
It really sucks to have such a primitive problems annoying users alot for a long time, try to fix it already, JIRA team.
I was struggling with this for a while. I think at some point #ISSUE was working, then [ISSUE], now I found couple ways it works both with actual links.
I have put all my attempts into the video, in case someone finds this way easier to learn: https://www.youtube.com/watch?v=USj7HKy1u6w
Entering issue number in square brackets like [ABC-100] work, but Jira converts it to an issue link after you post the comment. Until then you will see it as just plain text.
Just wasted 2 hours on this without saving the comment. Jira converts user mentions without saving the comment and I assumed issue linking would also work the same way.
For me it works if I hit Enter after entering the ID, but it does not work if the ID is the on the last line it seems. Should be easy to fix!
EDIT: Several weeks later I understood there has to be white space (space or line break) after the ID to get the automatic conversion
Maybe something went wrong over the week-end with the Atlassian cloud instance of JIRA & Confluence, but it seems like I lost my inline link's summary for a peculiar reason.
If I look at a JIRA Description, I get this :
and under Confluence I get this :
Before we installed confluence, the link summary in JIRA was perfect and verbose, suddenly or after a potential bad move of one of our admin, our JIRA's links are broken.
I can't find anywhere to configure them. I don't have jira.projectkey.pattern in my advance settings and no way to add any.
Any help on this will be really welcome
I cannot see any Advance Settings in the General Configurations. In the Atlassian documentation I found that The Advanced Settings button is only visible if you have the JIRA System Administrators global permission. (https://confluence.atlassian.com/display/Cloud/Configuring+JIRA+Options), but in my instance there is no trace of JIRA System Administrators permission (neither the administrator who created the instance has it). Could you please tell me how can I modify the Advance Settings ?
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