Can Automation for JIRA assign a task to the next available fixVersion?

[bidorbuy tech]

We use Fabric.io to automatically log JIRA tasks for our mobile projects. Ideally I would like to automatically assign the fixVersion and affectsVersion.

In our case we have a versioning scheme of Major.Minor.Patch (i.e. 2.6.5) and the affectsVersion would be the last released version. The fixVersion would be the first unreleased version.

Is this possible at all to configure via Automation?

[Nick Menere · Accepted solution]

Hi,

Thanks for using Automation for JIRA.

Unfortunately we can't do this but I think it is an awesome suggestion. I've raised this as https://codebarrel.atlassian.net/browse/AUT-211

We've got some high priority items on the go at the moment but I'd love to get to this soon.

Cheers,

Nick

[bidorbuy tech]

This is great news.

[Nick Menere]

Just an update on this:

You can now set the fix version to the following options: "Last released version", "Next unreleased version"

[John John]

I see the new choice in the drop list but no value is being applied.  I assume I may have my versions defined incorrectly.  How does the automation determine the 'Next unreleased version'?   I.e.  Does it grab the first unreleased version as sorted on the Versions page or does it do some analysis of start/end dates?

Thank you

[Nick Menere]

Hey John,

We get the list of versions from Jira in created order. We then find the first version that is not released and not archived.

If you are seeing this, please raise a support case and we dive deeper into it.

Cheers,

Nic,

[Artem Usov]

Hi https://community.atlassian.com/t5/user/viewprofilepage/user-id/502194 

I've set up 'Next unreleased version' to be populated in Automation and in test had 2 unreleased versions.

In test second one (which is second in Versions) added into the ticket instead of the first one.

Does 'Next unreleased version' mean that actually 'next' is the 'next after first unreleased' ?