Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

How to get issues only for next unreleased version

Josef Micka
Contributor
November 21, 2018 edited

OK i will explain what i exactly i need.

atm. when solving "issues" for next release we mainly use 2 filters

 

current release filter - which main condition is fixVersion = earliestUnreleasedVersion()

future release filter - which main condition is fixVersion > earliestUnreleasedVersion()

these filters work well, and whenever we release version (Trough version management), boards update without issues.

now there is real question, since there are multiple people in team, and not everyone has work in "current release", i want them focus on "next release", while they see issues on "future release", they can pick from issues with lowest "fixVersion",  but for better organization (and also easier planing for sprints) i really would like to make make board with filter for next release after earliestUnreleasedVersion()

earliestUnreleasedVersion() + 1 doesn't work (obviously)

 

with our release cycles we plan work ahead, and issues are spread(planned) 5 versions ahead (not counting special "FUTURE" version, which holds anything that is planned, but not in near terms, issues from there are moved to real version, when their time comes).

 

so let's say i have versions (for simplification i use year and month in sample - although are cycles are shorter)

2018-10 - released

2018-11 - current release worked on - not released yet

2018-12 - next planned release version

2019-01 - next planned release version

2019-02 - next planned release version

 

i can use  fixVersion = earliestUnreleasedVersion()  to see 2018-11

i can use  fixVersion > earliestUnreleasedVersion()  to see 2018-12 and other future versions

what i want to see is 2018-12, without need to change filter every time we release version (let's call it "next release filter")

when we release 2018-11 i want to have filter for 2018-12 (current release filter), but also for 2019-01 (next release filter)

 

have not found, how can i do that.

 

1 answer

4 votes
Henrique Bittencourt
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 27, 2018

Hi Josef!

So, about your question, unfortunately, there isn't a nextUnreleasedVersion() function to help you with.

Digging a little further on the JAC I've just found this feature request:

Allow filter by "Next Unreleased Version"

But it was marked as fixed, please take a look into this comment.

Seems like you can search using the following statement:

fixVersion = earliestUnreleasedVersion()

Also, take a look into this comment:

This function appears to use the order of the "Versions" in the list NOT the dates associated with them. Also, note the list earliestUnreleasedVersion() function expects the next list to be ordered with the old/next versions on the bottom of the list with future versions on the top. (I.E. From top to bottom: Release 6 -> 5 -> 4 -> 3 -> 2 -> 1 NOT Release 1 -> 2 -> 3 -> 4 -> 5 -> 6).

Hope this can help you out.

Best Regards.

Josef Micka
Contributor
November 27, 2018

Thanks for your reply.

Our versions are ordered correctly, so when i mark version as released correct version become “earlieastunreleased”.

now what i want is function that wil get me earliestunreleased() + 1, or if you prefer functional approach earliestunrealeased().next()

if there is no such functionality in jql, then i will stick with redoing filter for next unreleased manually, like i did until now, but it would be nice to have feature.

but i’m asking here, because someone might have needed this too, and solved it.

regards

Like 22 people like this
Lacey McDonnell
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 26, 2021 edited

@Josef Micka you might have more luck if you combine some of these statements.

fixversion not in (earliestUnreleasedVersion()) AND fixversion not in releasedVersions() AND project = PROJECTKEY

This at least gives you the remaining future fix version issues. You can then filter by Due Date or some other marker to see what needs work now.

Like 3 people like this
Ludmila Romash December 20, 2021

@Lacey McDonnell, hi!

I have a problem,  earliestUnreleasedVersion() always back No result value.

I have release dates and releases. 

Tommo
Contributor
June 23, 2022 edited

@Ludmila Romash  FYI I get results for the filter (works for me):

fixVersion = earliestUnreleasedVersion()

 

Like CodingCam likes this
Ludmila Romash June 24, 2022

@Tommo for some reasons, it works for not started release, I can't see current release with this filter.

But, thank you, I noticed that now it works

Like Tommo likes this

Suggest an answer

Log in or Sign up to answer
TAGS
atlassian, atlassian government cloud, fedramp, webinar, register for webinar, atlassian cloud webinar, fedramp moderate offering, work faster with cloud

Unlocking the future with Atlassian Government Cloud ☁️

Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.

Register Now
AUG Leaders

Upcoming Jira Events