grouping releases

[David Castro]

Hi! well here is my issue:

We have 2 different versions in our product,  version A and version B, but every sprint (4weeks) we release a new version of each one, the releases have their version number (e.g. V2.2.3), now when a bug is reported in Jira I wanted to know if it was created in the version A or B, meaning that i would need to group these releases into the versions to identify them.

I was thinking something like creating two versions and then sub-versions ta merge into them, so we could know which version is the affected (A or B) and which sub-version (e.g. V2.2.1).

[John Funk]

Hi David,

Why don't you just include the name of the product in the version name? 

[David Castro]

Hi John,

We can't do it because A and B will always remain the same... some similarity is like having a "production version" and a "testing version" so everytime we release one we have to include it into one of those.

[John Funk]

Sorry, I read that wrong about the product name. I would still give the version names some unique identifier other than just numbers. Like Prod-V2.2.1 and Test-V2.2.1