nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JQL to get all linked delivery tickets within a specific JPD project

Gary Spross_k6wgpo

Is there a way to write a JQL statement that would return all linked delivery tickets from within a JPD project?

Example:

Return all Epics tied to Initiatives linked within JPD project X.

If that's to much, what about:

Return all delivery tickets linked within JPD project X.

Accepted answers

Bill Sheboy

Hi @Gary Spross

Short answer: I do not believe it is possible to get them for a specific JPD project using out-of-the-box JQL.

If you want issues probably linked as "Delivery Tickets" to any JPD project Ideas, that would be the following, using the internal, link type name used by JPD:

issueLinkType = "Polaris issue link"
 AND issueType != Idea
 ORDER BY Key ASC

As an aside...one would think this would be better, using the externally-facing name of that link type:

issueLinkType = "Implements"
 AND issueType != Idea
 ORDER BY Key ASC

However, that link type may be used to connect anything to anything else, and so using the internal name may be better.

UPDATE: It appears when linking any two non-Idea issues using "Implements", it adds the Polaris type behind the scenes, even though they are not JPD related. This seems like a bug to me, although probably just inherited behavior as "Delivery Ticket" functionality is just reusing issue linking.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Gary Spross

Short answer: I do not believe it is possible to get them for a specific JPD project using out-of-the-box JQL.

If you want issues probably linked as "Delivery Tickets" to any JPD project Ideas, that would be the following, using the internal, link type name used by JPD:

issueLinkType = "Polaris issue link"
 AND issueType != Idea
 ORDER BY Key ASC

As an aside...one would think this would be better, using the externally-facing name of that link type:

issueLinkType = "Implements"
 AND issueType != Idea
 ORDER BY Key ASC

However, that link type may be used to connect anything to anything else, and so using the internal name may be better.

UPDATE: It appears when linking any two non-Idea issues using "Implements", it adds the Polaris type behind the scenes, even though they are not JPD related. This seems like a bug to me, although probably just inherited behavior as "Delivery Ticket" functionality is just reusing issue linking.

Kind regards,
Bill

Gary Spross_k6wgpo

Ah, ok. I figured this might be a bit to much for native JQL. We don't have ScriptRunner, but I wonder if there are functions available in that app that would allow for more granular, specific searches such as this.

Thanks for the input!

Bill Sheboy

Here is another way to see them all, but as references to the Ideas instead. The results could be exported to get the links.

navigate to Filters > View All Issues
add links to the columns
use JQL to select the Ideas in your JPD project which have links

project = myJPDProject
 AND issueLinkType = "is implemented by"
 ORDER BY KEY ASC

This solves the problem of someone incorrectly using the "Implements" link for other project types.