Thanks in advance for any comments (nice ones please, this isn't Twitter!). I have a general question regarding managing the builds and versions that sprint items are being released in.
The following is an example of how we work 'in real life', and I'm trying to work out the best way to use Jira for this. We produce a series of interm testing builds/versions until a sprint is completed and then a final customer release build/version. It may go something like this:
My question is, what should I do with all these builds in Jira? Currently, each time we produce an interim build for testing, we create a new version and record this against the sprint item 'Fix Version'. So, in the above example, the first 3 sprint items would have a 'Fix Version' of v02.03.01.
The problem is, it starts to feel a bit messy. We can end up with multiple versions listed (one for each of the times we have produced an interim testing build). These all relate to only 1 actual customer release build. So, in the releases section we may have v02.02.03.01, v02.03.02, v02.03.03, v02.03.04, v02.03.05, v02.03.06, v02.03.07, v02.04.01, as shown below in the screenshot.
Do any of you produce a version for each interim build and record it in Jira? Do you archive off the interim testing versions? Do you use the merge versions option?
If I carry on as I have described, when running a query to find all the sprint items in a release, I have to search between v02.03.01 and v02.04.01, rather than just the customer release version of v02.04.01.
I feel as if I am doing this in an inefficient way (or maybe the phrase 'just completely wrong'!).
Any opinions would be welcome.
You may try to merge interim releases to final customer release. That is you can merge v02.03.01, v02.03.02, v02.03.03 to v02.04.01. At the end, you are actually releasing v02.04.01 version to customer.
You can use betweenVersions JQL of our "Configuration Management Toolkit for JIRA" app. But I think it is a little overkill and using build-in merge function is a lot easier.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
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