Menu
We often have issues reported in JIRA for multiple versions of an application. However the fixes for these issues are not commited at the same time for every version the issue is reported for. This makes it hard to track in which version a fix was commited and developers sometimes forget to commit a fix for a version.
Is there a way to track the status of an issue for each version where it is reported separately, but in the same issue? In addition to a single status for an issue (which is only updated to a status when all versions have that status, i.e. an issue is set to "resolved" when it has been resolved in all fix versions), I would like to see a different status for each fix version.
After looking on the Atlassian-page I found an old issue in their JIRA which requests such functionality. Related to that there are forum discussions which suggest using a sub-task for each version. This would be a good solution if there was a plugin to automatically create the sub-tasks upon issue creation and fix version update. Is there such a plugin?
608
Affects version is the version in which a bug or problem was found. Although it can be useful for tracking problems, it isn't used very often in Jira. Fix version is the version where you plan on releasing a feature or bugfix to customers.
Releases represent points in time for your project. They can be used to schedule how features are rolled out to your customers, or as a way to organize work that has been completed for the project. In Jira Software, each release is called a version. For more information, you may refer to Releases and versions.
On the Versions screen, hover over the relevant version to display the cog icon, then select Release from the drop-down menu. If there are any issues set with this version as their 'Fix For' version, Jira applications allow you to choose to change the 'Fix For' version if you wish.
You don't need a plugin. You can easily do this using standard JIRA functionality.
Just create a JIRA issue documenting the bug and then create sub-tasks for each version you want to fix the bug in. I usually use the parent issue to track fixing the issue in the latest (unreleased version).
In your JIRA configuration it might help to create a custom sub-task issue type called "Backport" to distinguish these issues from generic sub-tasks.
95
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
