fixed version tied to sprint and build

[prempal singh]

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

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

[Boris Berenberg]

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: https://docs.atlassian.com/jira/REST/latest/#d2e335