Writing a JQL query to pull all tickets that have ever been deployed

[Eman Khan]

I have a request from my client where they want all jira tickets that have been deployed in past releases.  I'm trying to find the best way of pulling this data via JQL.  The field that we normally pull would be by the fixversion however i feel like the naming convention has changed over the years.  My ask is, I need some help with the JQL query to be able to pull all tickets that have ever been deployed.  The fields I'm trying to pull are:

Key

Summary

Fix Version

Release Date

[Michael Garzancich]

Hi there!, from what I understand is that you would like to to pull all Jira tickets that have been deployed in past releases, where the naming convention of the Fix Version field might have changed over the years.

In this case, try use the JQL query :

fixVersion is not EMPTY AND fixVersion in releasedVersions()

After running the JQL, In List View, to ensure you get the fields you're interested in (Key, Summary, Fix Version, and Release Date). You can Configure the columns (top right) shown in the Issue Navigator to include your desired fields.

Hope this helps!

[Eman Khan]

so after searched by this JQL, i'm unable to switch back to basic to update the other columns

[Michael Garzancich]

You won't be able to switch to basic as the Query is too Complex but while you are still in advanced JQL mode you can Configure the columns. 

Please Find attached screenshot for reference:

[Eman Khan]

is there a way to also include the field 'linked issues' to the above sql? I want to make sure that field is not empty

[Michael Garzancich]

fixVersion is not EMPTY AND fixVersion in releasedVersions() AND issue in linkedIssues()

[Eman Khan]

so i realized there are multiple links for each baseline...i think i want to specify that the linked issue starts with "RMT

[Michael Garzancich]

Hi @Eman Khan 

Unfortunately, in Jira's native JQL, you cannot directly query linked issues using only the key pattern (like RMT). The linkedIssues() function does not support filtering by issue key or key patterns.

This will not work because the linkedIssues() function is designed to work with link types, not issue keys. It looks for the type of the link between issues (like "blocks," "is blocked by," etc.), not the key of the linked issues.

Hope this helps!

[Charlotte Santos -Appfire-]

Hi @Eman Khan 

I’m Charlotte, a support engineer at Appfire and I’m here to help you.

Unfortunately, natively, you’ll not be able to do it dynamically.

In the app where my team works, JQL Search Extensions for Jira, you can use this query to get all issues whose fix version is released:

fixVersionsReleased > 0

Please contact our support if you have any other questions about this query, or the app in general.

We’ll be happy to help you! 😉

[Marco Brundel]

Hi @Eman Khan ,

If the field 'fix version' is filled when a issue is deployed, you can use the JQL:

project = "YourProjectName" AND fixVersion IS NOT EMPTY


regards,
Marco Brundel