JQL to display issues in release only if all issues are in a specific status

[Dave Furlani]

We'd like to have a filter that shows tasks that are in a status of Complete that have a release (fix version) set, only if all the tasks in that release are in the status of Complete. If any task in that release is in a different status then we don't want any results. All or nothing.

We don't want to have to update the version number every new release. A single query that capture the short moment in time before a release, while we're doing UAT, that the devs believe their tasks to be a release candidate. 

Is that possible?  If so, please advise how?

Thanks

[Dave Furlani · Accepted solution]

It seems this is not possible to show on a kanban board because the filter can not do what we need to populate the board

[Rilwan Ahmed]

Hi @Dave Furlani ,

Welcome to the community !!

Please try the below JQL after modifying to fixversion, Project value and let me know if it works for you or not. 

project = SANDBOX AND fixVersion = 10000 AND status = Complete

[Dave Furlani]

We don't want to have to update the version number every new release. Sorry, I should have been cleared. I'll edit the original question now.

[Rilwan Ahmed]

Hi @Dave Furlani ,

Please try these:
1. fixVersion = earliestUnreleasedVersion(projectKey) and status = Complete.
Perform searches based on the earliest unreleased version (i.e. next version that is due to be released)

2. fixVersion in unreleasedVersions(SANDBOX) and status = DONE
Perform searches based on the unreleased versions (i.e. versions that your JIRA administrator has not yet released) of a specified project

Please note: You can also search on the unreleased versions of all projects, by omitting the project parameter

You can find all JQL functions related to releases in https://confluence.atlassian.com/jiracoreserver073/advanced-searching-functions-reference-861257222.html 

[Trudy Claspill]

Adding to @Rilwan Ahmed 's answer, note what "earliestUnreleasedVersion" means:

Version order is determined by the order versions are placed in on the Releases page in the project. The version at the bottom of the list is considered the "earliest." To change the order of versions, drag and drop them to a new place in the list

[Dave Furlani]

@Trudy Claspill When you say "earliest", do you mean the bottom version is considered, "Next out the door"?  If so, does that mean the release date is ignored?

@Rilwan Ahmed While that is a function I was not aware of, I suspect it will give results even if only 1 of the N tasks in the release are in the status of Complete. I'm hoping to see no results until all tasks in that release are marked as Complete. Is that possible?

[Trudy Claspill]

Hello @Dave Furlani 

That quote is directly from the documentation that @Rilwan Ahmed linked in their response.

And, yes, the release date information is ignored. It is all about the position of the version in the list of unreleased Versions.

[Rilwan Ahmed]

Hi @Dave Furlani ,

This is not possible in native jira functionality. 
"I'm hoping to see no results until all tasks in that release are marked as Complete. Is that possible?"

[Dave Furlani]

Yeah, I thought not. Nice to have my thinking confirmed. Thanks.

My plan B is to use automation. I can count the number of issues in the release and the number in the release in the Completed status, compare those numbers and send an email if they're the same. It's not in the Kanban board like had been hoped, but it's better than the current approach

[phalgun_reddy]

Hi @Rilwan Ahmed @Trudy Claspill 


Greetings!!!
I am new here is there any JQL to find the no of releases created in certain period of time (23-Mar-2022  -   23-Mar-2023)

please do the needful.

Thanks

phalgun 

 

[Trudy Claspill]

No, JQL is used to retrieve issues.

[Trudy Claspill]

Hello @Dave Furlani 

Welcome to the Atlassian community!

I have some questions.

Are you wanting to get results for a specific Fix Version value, or do you want this for any and all Fix Version values where the Fix Version includes only Completed issues?

An issue can have more than one Fix Version value assigned to it.

Do you want the issues regardless of the various Fix Version values assigned, as long as one of those Fix Versions is comprised of only Completed issues?

Do you have any JQL-extending third party apps installed on your Jira instance, such as the ones found in the Atlassian Marketplace here? If so, which one?

https://marketplace.atlassian.com/search?hosting=cloud&product=jira&query=jql

I don't believe you can get that information with native Jira JQL functionality. There is not a JQL feature that would determine that some, none, or all of the issues in a Fix Version are in a given Status with a single JQL filter without a person reviewing the filter results. There may be a feature in a third party app that would help with this.

What do you want to do with the results? I believe there is a way to get the information through an Automation Rule, but if you want to display the results in a Dashboard that would not help you.

[Dave Furlani]

Hi @Trudy Claspill , To answer at least some of your questions...

I don't believe you can get that information with native Jira JQL functionality.

I agree with you. I was pretty confident that what was asked of me wasn't native Jira behaviour.

What do you want to do with the results?

The desire is to have this appear on a board of some sort with near live results, like a dashboard or in a column on a kanban board (because of the single status). Tasks in that status are ready for UAT, but we only want to call in the business SMEs once (i.e. when all the tasks for that release are Complete).

Do you want the issues regardless of the various Fix Version values assigned, as long as one of those Fix Versions is comprised of only Completed issues?

Yes please. This should negate any concern of some tasks having multiple versions, and reduce the need for naming the specific version in the filter.

Do you have any JQL-extending third party apps

Not really. Apps that we have that might help are:

• JIRA Toolkit Plugin
• JSU Automation Suite for Jira Workflows
• Octopus Deploy
• SpiraTest Add-on for Jira
  

I could probably convince my exec to approve budget for the very popular add-ons, such as ScriptRunner or JQL Search Extensions. The add-on would need to have a lot of be maintained and have community support, etc. so as to only have a low future deprecation risk.