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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Is there logic to have a field populated with the next unreleased version that ends in ".1"?

I am looking to utilize an automated rule that will populate the next unreleased version (that ends in ".1") into the fix version field, upon being transitioned into a specific status.

Presently, our Fix Version releases have naming conventions that are labeled as "v.3.55.1", where "v.3.55.2, v.3.55.3, etc." would be hot-fixes.  In the rule, the goal would be to have the field populated with the next unreleased version that ends in ".1", in order to avoid the issue being updated with a hot-fix version.

The logic to pull in the next unreleased version exists, though it does not address the issue in which we are attempting to resolve. I am hoping to receive feedback in reference to how to have the version selected based upon the criteria of ending with ".1"


1 answer

0 votes

Hi @Davielle Boyce-Hotz -- Welcome to the Atlassian Community!

Short answer: no.

Longer answer, and possible work-arounds:

In Jira, the "next unreleased version" is the one at the bottom of the list in the release/version list (without changing the sort order in that view).  If your ".1" version is at the bottom of the list, you could find it just using the built-in rule features.

If it is not the "next" one, and there is one-and-only-one unreleased version with a ".1" at the end of the name, you could call the REST API to get all versions for the project, using a rule's web request, and then filter to find the correct one.

Otherwise, this may not be possible as I do not believe you can access the ordering of the versions from outside of the user interface with out-of-the-box Jira features.  There might be a marketplace addon which can help with this.

Kind regards,

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events