I am wondering suggested best practice for logging bugs in JIRA Agile issues.
When a story/task/subtask is ready for review on dev or test and issues are found that need to be addressed within that issue during our current sprint, they are logged as comments by QA and then reassigned back to the developer. This repeats until no defects are remaining or the sprint ends, in which case the remaining known bugs are then logged as follow-up issues for a later sprint.
Keeping bugs like this in the comments is messy and convoluted. I would like to find a simple, efficient replacement. I have considering requesting that all bugs are logged as issues and linked back to the parent issue but am afraid it wont be effective given that there can be many of little defects (+20 taking under 10 min to fix, each) with very rapid handoff back and forth between devs and QA.
How are you tracking bugs in an issue before rolling out to production? To be clear we are utilizing capture for logging live bugs and that process is working awesome.
One possibility might be using epics. You could create an epic as the parent level, and then each JIRA issue could be the task/subtask. See https://confluence.atlassian.com/display/AGILE/Working+with+Epics
Also, here is a nice blog that details the estimation factors to consider:
...It's true that there are projects in Jira; but they are merely a way to cut off issues, to tell them apart from other sections of work and to apply rules that are specific to that team (the schemes)....
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