Uploaded image for project: 'Jira Cloud (including JIRA Core)'
  1. Jira Cloud (including JIRA Core)
  2. JRACLOUD-25640

JQL function for showing all issues linked to any issue by a given issue link type

    XMLWordPrintable

    Details

    • Feedback Policy:

      Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    • UIS:
      121

      Description

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Atlassian Update – 4 January 2016

      Hi everyone,

      Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days; unfortunately we don't have any plans to support this in JIRA for the foreseeable future.

      There are also a few add-ons on the Atlassian Marketplace that offer this feature if you're using JIRA Server (and several developers are looking at bringing this to JIRA Cloud also).

      Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Dave Meyer
      dmeyer@atlassian.com
      Product Manager, JIRA Platform

      originally copied from this comment

      Function linkedIssues() only shows the issues linked to a particular issue, I want to find all issues those are linked to other issues marked by a specific link type, e.g., "is blocked by".

      This function could incorporate querying issues that are linked to any issue with a given link type and bearing in mind that links have two identities, one in each direction, the link type could be direction specific or not.

      Examples

      1. find all issues that are duplicates of issue JRA-25640 (one direction, issue specified)
      2. find all issues that are blocking issue JRA-25640 or that JRA-25640 blocks (bidirectional, issue specified)
      3. find all issues that are duplicates of any issue, or which duplicate any issue (bidirectional, no issue specified)
      4. find all issues that are blocked (one direction, no issue specified)
      5. find all issues that are linked to a specific issue and display those based on a specific depth (linked issues displaying linked relationship two, three, etc., issues deep)

      Implementation Notes

      • The JQL function that exists must continue to work exactly as it does. If it is possible to overload the JQL function based on arity and this makes a consistent API, then this would be preferred. Otherwise, there may need to be a new function name which provides vararg behaviour as described above.
      • The link index entries added in 4.4 (I think) provide enough to build performant lucene queries for the above use cases. What's missing is the JQL function plumbing.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              chris@atlassian.com Chris Mountford
              Reporter:
              chris@atlassian.com Chris Mountford
              Votes:
              789 Vote for this issue
              Watchers:
              428 Start watching this issue

                Dates

                Created:
                Updated: