fixed version tied to sprint and build

As a program managerilike to define a product release version as 6.1 andwantthe Scrum master to later add the next suffix 6.01.02, i.e. 02 when he is planing the Sprint. And later on when the build isdone theycan update the story with two additional suffix 03 to designate which build the story went in.

6.01 is the product release number

0.02 designate Sprint the story is in

0.03 designate the Build the story is in

Soiknow clearly wheniwant to find out about a story which system release, which Sprint, and in which build it was introduced.

If there is a better way already implemented in Jira, please let me know. Thanks...

1 answer

0 votes
Boris Berenberg Community Champion Mar 18, 2015

You could do this, but you would need to have a mechanism to create and set these versions. I would consider having your build scripts pull the existing info from JIRA via our REST API, and then create these new versions using the API as well:

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,826 views 12 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot