i have a question regarding what to do with a user story when a bug is found. I see two scenarios :
1) You open a bug. But then, what do you do with the user story ? What state should it be put it ?
2) You put the user story at a failed status, describing the bug in its comments.
I'm not a big fan of the second scenario, because you can easily loose yourself if there are too many comments.
But for the first scenario, i don't know what to do with the user story while the bugs are being fixed.
Any ideas ?
Thanks in advance !
This really comes down to preference and what works best for your team. You could create a literal workflow that has an “in test” status and either move to Done if it succeeds or Failed if not. The developer would then move back to In Progress and address the bug. The other method would be as you stated in #1 where a separate issue is created to capture the bug in which case the tester should link the two issues and assign both back to the developer. The latter allows you to track multiple bugs against the story more definitively.
An option is to leave the Story where it is and flag it as impeded or blocked.
To flag an issue:
An alternative I've seen used is to add a new sub-task issue type - Defect. This is a bug found during story delivery which impedes the story's progress.
Bugs are then used for production bugs (i.e not located during development).
If you wanted to visualise Defects you could have them visible on the board - we decided instead to have a quick filter visualising which stories had an attached Defect.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events