We have one product which we maintain about 6 versions of (each on a separate branch in Git).
When filing a bug, we want ONE issue in which we describe the product bug itself (how to reproduce, effects etc).
We want something else to represent the fix of the bug on one Version/branch, in order to be able to keep track of in which Versions/branches we have merged the correction.
(Most often it is one and the same team that handles the correction of the bug on all relevant branches, but sometimes the correction is not done to all branches at once)
We use Git in Stash and want to make use of the power of tying Git commits to our Jira issues.
What would be the best approach for us in Jira?
Our initial idea was to use an Issue of type Bug for the product bug, and a Sub-Task to represent a fix on a specific Version/branch.
The drawback that we find with that approach is that the Sub-Tasks cannot be scheduled in individual Sprints.
Another approach would be to use an Issue of type Bug for the product bug, and one Child Issue of type Bug to represent a fix on a specific Version/branch. The drawback is that the relation Child-Parent is not as obvious as Issue-Subtask, but the advantage is that we can schedule Childs individually.
Is one of these approaches better than the other for us, or are there other approaches that would be even better?
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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