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?
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?
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' ?
Atlassian's marketplace partners have had a very productive start to 2021! Since our last roundup, our developer community has added over 160 new cloud apps to the Atlassian Marketplace to help you...
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