Have 2 version set up for test:
Set up an Automation to add 'Next unreleased version' to tickets after status changed.
Moved a ticket and Automation added a 'ver2' (30/July/2020 as from screenshot) value into 'Fix version' field instead of 'ver1' which was expected.
I saw a comment that versions for that action picked up by creation date, but I cannot find any way to see creation dates of my versions to confirm that it's the case for me.
@Kevin Bui Hey, thanks. It worked. So for anyone who also will got this 'issue':
Reorder your versions and expect:
That probably my misunderstanding as I understood 'Next unreleased version' as literally 'next' one or 'the first one' in the list of 'Unreleased' but it seems to be 'the next after the first (if there is more than 1)'.
@Kevin Bui - It doesn't seem to function that way on my Jira instance. I have 4 versions and it always gets set to the last of the 4 versions. It appears to always just pick the last item in the list regardless of the number of items.. Generally you would sort your items from top to bottom and expect it to grab the top item. I think there is still a bug and because it instead grabs the bottom item.
Since our last roundup in April, Atlassian's Marketplace Partners have added over 100 new cloud apps to the Atlassian Marketplace to help your teams work more efficiently. Let’s take a quick look a...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events