1. A user reports a bug. 2. The developer identifies that the bug applied to other branches. 3. The developer clones the bug, which automatically creates a copy of the bug and allows the developer to edit it before it gets submitted. The user edits the version to which the issue applies. 4. The created clone automatically gets a child relationship with the original bug, but this can be changed as part of the editing done in step 3. 5. By doing the above process it is easy to keep track of the branches that the bug applies to, in which ones it was fixed, the modifications done in the code (if your soure control tool is integrated), and the bug summary appears also in the auto-generated change log of these branches.
The above achieves the power of tracking the issue on each branch with minimal overheads on the developer.
Slashdot Mirror
Mantis Bugtracker ( http://www.mantisbt.org/ ) handles this as follows:
1. A user reports a bug.
2. The developer identifies that the bug applied to other branches.
3. The developer clones the bug, which automatically creates a copy of the bug and allows the developer to edit it before it gets submitted. The user edits the version to which the issue applies.
4. The created clone automatically gets a child relationship with the original bug, but this can be changed as part of the editing done in step 3.
5. By doing the above process it is easy to keep track of the branches that the bug applies to, in which ones it was fixed, the modifications done in the code (if your soure control tool is integrated), and the bug summary appears also in the auto-generated change log of these branches.
The above achieves the power of tracking the issue on each branch with minimal overheads on the developer.