+1 vote
How should we track a bug through multiple branches?

We usually have several active code branches, and some bugs need to be fixed in more than one of them. For branches that are no longer synced from their parent branch (so fixing a bug is done on each of them separately), we created different Workflow Events, paired with automatically updated custom fields for status tracking. When a new branch like this is created, we must create new fix/verify events, custom fields, automation rules, pop-up values, which is too much work and possibility for errors, and as we abandon old branches, many events and custom fields remain in the project that are no longer in use. I started to work on refactoring our Helix ALM workflow, and I'd be happy to hear others' opinion on this particular problem. Thanks!
asked Oct 20, 2017 in TestTrack by lkocsis (210 points)

Please log in or register to answer this question.

248 questions
262 answers
2,047 users