Jira could do with “Split version” option for Roadmap
I often find that when reality catches up with us, we need to bail out a bunch of issues that just can’t be fixed in our current release version unless we introduce unacceptable delays in the release.
When this happens I have to use “Bulk change” in Jira’s issue navigator to locate the subset of issues that are going to be “bumped” and change their Fix-for version to the next version.
However sometimes we need a new version inbetween the current and next, to handle those “bumped” issues. i.e. version 1.0.14 was going to have X and Y in it, and 1.0.15 is going to have P and Q in it. After bailing out issues that can’t be fixed for 1.0.14 we really need 1.0.15 et al to be moved up a revision number (to become 1.0.16 containing P and Q and so on), and a new 1.0.15 created containing just the issues bailed out from 1.0.14.
Because Jira is not version-number aware currently, it cannot do this. It could currently offer a “Split version” option in the Version Management page, so you could instead of Releasing make it “Split” the version into resolved and unresolved issues, and prompt for a new version number to sit in between this and the next release. So we could enter “1.0.14b” for example.
It’s not perfect – auto version numbering would be much better – but it would do until that comes.
No related posts.
