Keeping Track of Tickets that don't pass QA

Question

Currently we use story tickets for our primary product requirements. Those tickets then get assigned to QA once completed by dev. If the ticket doesn't pass QA then our testers are using bug tickets to track what issues they're finding, reproduction steps, etc. They link these bugs to the original ticket but its still a HUGE mess to keep track of. Often I'll have my story ticket showing as in QA but the two bugs associated to it are back in dev. What's the best practice here? Should we not be creating bug tickets when a story ticket doesn't pass QA? And if not, then where do the testers put their feedback? Thx!!

Callum Carlile _Automation Consultants_ · Answer

Hi @Kelly Krause , welcome to the Community!

I would suggest that you probably don't need to raise a bug for something that is not yet released, but instead you can add a transition in your workflow which goes back from the testing status to an 'in dev' or 'ready for dev' status (or whatever you want to call them).

On this transition, you can add a transition screen where the testers can add comments and say why the test has failed - you could even add a validator to force this comment if you wish.

Hope this helps!

Trudy P Claspill · Answer

Hello @Kelly Krause

Welcome to the community.

What is the workflow for the story? Is QA a status for the issue, or do you just change the Assignee to a person in the QA team?

Do you require the Bugs to be resolved before the Story can be Closed? Or is that decided on a case by case basis?

Does the issue remain assigned to QA with addition QA activity happening while Bugs are being worked on?

If the QA work is completed and there are Bugs to address do you leave the issue assigned to QA or do you assign it back to Dev?

Are you working in Sprints? Do you plan Bug work in your Sprints with Estimates like you do your Stories?

How is your Release practice tied in to this? Can you Release the code for the Story before the Bugs are addressed?

We need to know more about your work practice to provide good advice.