In traditional project management, bugs are often separated from requirements or even managed in dedicated tools named “bug trackers”. In agile methodologies, if you keep separate backlogs for user stories and bugs, then the Product Owner cannot clearly materialize their vision, developers don’t know what to implement next and stakeholders don’t know what to expect next. For it to be effective, there must be one and only one unambiguously ordered Product Backlog.
For this reason, bugs are managed as stories in iceScrum and receive very little special treatment. If you further think about it, user stories and bugs are actually not so different: both express a desired behavior that the product does not currently offer.
Only two fields differentiate defect stories and user stories:
Creating an effective defect story is as simple as filling these fields in combination with regular story fields, e.g. a proper description, attached screenshots to demonstrate the issue and a dependency to the done story that it relates to.
Defect stories then follow the regular story workflow.
The story template App allows pre-filling stories when you create them. Thus, you can define a “Bug” template with a default task list, e.g. “Reproduce the bug”, “Write a unit test”, “Solve the bug”…
If your stakeholders are used to using a separate tool, you can import issues as stories automatically thanks to Bug tracker Apps.
The Custom backlogs Apps allows creating filtered story view, e.g. a backlog that displays new bugs (the stories of type “Defect story” and state “Suggested”).
Finally, some metrics such as the project Burndown Chart and Backlogs charts allow to keep track of the evolution of defect rates, which of course you want to keep low.