JQL for earliestunreleasedversion is not working

[Daniela Cardenas]

I'm trying to run a query for the earliest unreleased version. project = "CircleBlack Development" AND fixVersion = earliestUnreleasedVersion()

It is pulling the version with the earliest start date (version "23.3.0") but not the earliest release date. It should be pulling up the 23..19 version. Why is this happening? 

Even just 15 minutes ago, it was returning the version "N/A" which is the only version without any release date or start date on it. Something is going on with this function.  

[Bill Sheboy · Accepted solution]

Hi @Daniela Cardenas 

When you navigate to the releases page, it displays the versions in order.  The one at the bottom is the "earliest unreleased version", and so on, moving up the page.  That is unfortunately the way the page is designed.  It does not use the release dates to determine "earliest unreleased".

If you have changed the order on the page, by selecting one of the column titles, that order is different.  To go back to the built-in ordering, leave the page and then navigate back to it.

To solve your need of having the releases in your desired ordering, use your mouse to grab the version name and you can drag it to the correct order.

Kind regards,
Bill

[Daniela Cardenas]

wow this is terrible logic! I may request an enhancement for this to work based on the actual release date field.

Thanks for your help. 

[Bill Sheboy]

There are several open suggestions to change that behavior, so look to see if there is one that matches your needs and vote for it; if not, please add one.

https://jira.atlassian.com/secure/Dashboard.jspa

[VINCENT DUPONT]

Hello

I confirm! The use of the ordering is very counter intuitive. Why not simply rely on the release date ??

Vincent

[Michel Rugenbrink]

Good to know it works on some internal order of releases, how do I change the order? Right now it has decided that the wrong release is the `earliestUnreleasedVersion`... so I'm looking to fix that, please tell me I don't have to throw away all existing releases and make new ones in the order I need as that's no workable solution.

We work with minor and patch releases. The next minor release is usually known well in advance, but patch releases are decided much later, but release in shorter development cycles. So if the creation order of the release decide that the next minor release is always the earliestUnreleasedVersion that renders the filter completely useless for us.

[Evie Z_]

This topic is now closed as the discussion has become outdated. If you have more questions or want to continue the conversation, feel free to start a new topic. For more details on why we close older threads, check out our Rules of engagement - Atlassian Community .

Thank you for your understanding!