I am trying to develop a better practice for managing and naming JIRA releases (versions) and associating JIRA issues with these. Here is the context:
Here is a diagram illustrating this:
I believe this is not that uncommon. Atlassian itself seems to be using 3-part version numbers as well and they are clearly developing these in multiple iterations.
Suppose the following cases:
My question is, how to organize this in JIRA.
If I create a JIRA release entry for each customer-facing version (i.e. 2.5.8), then I cannot associate issues with iterations or builds for internal use. I have issues with iteration planning (see case 1 above) and recoding issues that are relevant between iterations only (see case 2 above).
I am not sure how I could possibly create a JIRA release for each iteration, since the iteration does not end up in our version scheme. It could be made up (e.g. 2.5.8#1, 2.5.8#2) of course. However, this would render JIRA's release notes obsolete, as customers would not want to see release notes for an iteration, but cummulated for all iterations of a customer-facing version and they would not want to see "internal" issues that existed only between iterations.
I most likely do not want to create a JIRA release for each build.
Are there any best-practices how to do this? What methods are others applying?
I would love to hear your feedback and shared experience.
This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...
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!
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