Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-25640

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



    • 82
    • 82
    • 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.


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

      Atlassian Update – 11 September 2019

      This has now been implemented as the issueLinkType field, with the same behaviour as the equivalent, recently-added Jira Server functionality.

      Additionally, we've also added an issueLink field, which functions equivalently to the linkedIssue() JQL function, but is more discoverable and flexible.

      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.


      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.


        Issue Links



              Unassigned Unassigned
              chris@atlassian.com Chris Mountford
              791 Vote for this issue
              427 Start watching this issue