-
Suggestion
-
Resolution: Won't Fix
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Something like the linked issues feature. It would be great if someone mentions a ticket ID at the summary or any comment of issue A, a linked issue in issue B would appear that issue B has been mentioned in issue A. Kind of an automated issue link.
- is related to
-
- Closed
[JRACLOUD-46065] Link Issues mentioned a ticker id
Would also like this feature in Jira Cloud, please consider reopening this request.
We have several use cases for this feature:
1 - when we mention in comments of the new issue other tickets from the same Jira project and the same Type, e.g. if I mention in JRACLOUD-XXXX some other issue JRACLOUD-YYYY, it would be great if this issue is linked as mentioned in JRACLOUD-YYYY and vice versa. Otherwise we are linking them manually because in JRACLOUD-YYYY you can't see that it was mentioned by JRACLOUD-XXXX if not linked. It is used when issues have the same RC, resolution. So opening JRACLOUD-YYYY allows you to see how JRACLOUD-XXXX issue with the same RC was fixed.
2 - when we mention issues from different projects and different types, e.g. we have an issue type "Incident-XX" (project A) where we mention issue type "bug-YY" (project B). Currently we have to manually link the "bug-YY" to the Incident-XX. It is very useful to see how many incidents were already related to the same bug (or to some improvement, etc.) to prioritize it for developers or to see the status of the linked incidents in case if there are several incidents opened for investigation/analysis due to the same bug/improvement/etc. Incident-XX may include more investigation details then registered bug-YY thus when incident-XX will be automatically linked to the bug-YY it will be evident where the bug comes from.
+1 - this would be a real neat feature. Often times comments are added or summary and descriptions mention another ticket and then we have to go find that ticket ... Hope this progresses. Thank you
Hi everyone,
Thank you for bringing this suggestion to our attention.
As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Hi everyone,
Thank you for bringing this suggestion to our attention.
As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team!
Hey there!
We've been working on a solution for this issue that covers most of the use cases highlighted here, including:
Have a look here (Free to use during beta): Automatic Issue Links for Jira
If you want to discuss other use cases, we'll be happy to hear from you! Feel free to reach out: wilmer.medina@servicerocket.com
Thanks,
Wilmer M.
ServiceRocket.