JQL to filter out archived fixVersions

[matthew_bache]

Is there a way in native JQL (we do not have scriptrunner) to find tickets in released fixVersions, but not in archived fixVersions? It would be something like this:

project = DATA AND fixVersion in releasedVersions() AND fixVersion not in archivedVersions()

The requirement is to report on only tickets that have been released in recent and active fixVersions. We archive a fixVersion once a new fixVersion has superseded it.

Thanks

[Benjamin · Accepted solution]

Hi @matthew_bache ,

Unfortunately, There isn't a JQL for this natively. 

A ticket is raised for this:

https://jira.atlassian.com/browse/JRACLOUD-10692

The status is showing gathering interest.

Thanks,

Ben

[matthew_bache]

Thanks, Ben.

[Bill Sheboy]

Hi @matthew_bache 

How many issues are you expecting in the result set? 

If it is less than 100 you may find the issues with an automation rule.  You could run this rule whenever you need to know the issues, or even run it on a schedule (or other trigger).  Such a rule could be:

• trigger: let's use scheduled, but it could be manual if you wish
• action: lookup issues with this JQL, substituting in your project name, and any other criteria you wish

project = myProjectName AND fixVersion IN releasedVersions() AND statusCategory = Done

• action: log the results, or send an email with the keys of the issues by filtering the lookup as follows:

The issues in released versions, not archived are: 
{{#lookupIssues}}{{#if(not(fixVersions.archived))}}{{key}}{{/}}{{^last}}, {{/}}{{/}}

How this works...

• the lookup issues action gathers the issues matching your filter, up to a total of 100 issues
• we then use a list iterator to walk the lookup issues
• with smart value, list filtering to only grab issues where the version is not archived using conditional logic
• and finally list the keys in a comma-separated list

Kind regards,
Bill

[matthew_bache]

Hi @Bill Sheboy 

Thanks for the great solution. However, it's likely that > 100 issues would meet the criteria, so that solution won't work for us. 

Kind regards

Matt

[Bill Sheboy]

Matt, after reading another posting I learned they have loosened the limits up a bit and so a single query/trigger can do up to 1000 issues, and the total for a rule (if that 1k referenced others) is 5000.  There are other limits for processing time, but the 100 limit seems to be old info; sorry about that!

https://support.atlassian.com/cloud-automation/docs/automation-service-limits/