Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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?

2 answers

1 accepted

1 vote
Answer accepted
Nick Menere Community Leader Mar 14, 2017

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

This is great news.

0 votes
Nick Menere Community Leader Apr 10, 2018

Just an update on this:

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

Screen Shot 2018-04-11 at 10.17.19 am.png

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 Community Leader Sep 25, 2018

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,

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' ?

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

New Cloud Apps Roundup - April 2021

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...

317 views 3 20
Read article

Community Events

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

Events near you