How does bug tracking work in Scrumwise?

To track bugs in Scrumwise, add the bugs as backlog items of type Bug:

Adding a bug

A bug backlog item behaves very similarly to other backlog items, and you can include them in epics, releases, sprints, and Kanban boards, just like any other backlog item.

If you want to keep your bugs separate from your other backlog items, you can create separate backlog lists or backlogs for your bugs. For example, you can have a separate backlog for bugs, with backlog lists for each bug category.

A bug starts by being open. When you have solved the bug, either by fixing it or by finding some other resolution, you can mark it as resolved:

Marking a bug as resolved

When all work on the bug has completed, close the bug:

Closing a bug

Note that a bug isn't considered completed until it has been closed, regardless of its status or whether it has a resolution. For example, in the Backlog tab, if you select "Items not yet completed", you will see all open bugs, including bugs that have status Done or higher.

It is up to you whether you want to close a bug as soon as you have found a resolution, or you want to leave it open for now. Leaving it open is useful if somebody else must first verify the resolution, such as the product owner or a client. In that case, just mark the bug as resolved, and let the other person close it when the resolution has been confirmed. Otherwise, you can resolve and close it in one operation by clicking "Close this bug":

Resolving and closing a bug in one operation

Still need help? Contact us Contact us