The last article described one of the simple ways to use Zen Tao, that is, to use Zen Tao only for project task management. QA module in ZenTao can also be used separately. This method is very suitable for QA teams. The basic process of bug management in ZenTao goes as follows:

Testers identify bugs → Developers solve bugs → Testers verify and close bugs.

We will demonstrate the specific workflow as follows.

1. Create a product

The design philosophy in ZenTao is that bugs are mainly linked to products. We will explain the relations between products and projects later. Before managing bugs, you have to create a product first. Click Product-> Create Product.

When creating a product, you need to set up its name, code, and information about the person in charge. 

2. Report a bug

Once a product is added, you can report bugs. Go to Test->Bug and click Report Bug.

The required fields are some basic information, such as Title, Open Build, and Module when reporting bugs. 

Fileds like Product, Project, and Story can be ignored. 

A bug can be assigned to a certain person or leave it null if it is not sure who will fix it.

3. To process a bug

Confirm a bug: After confirming that the bug does exist, you can assign it to someone, and specify the type, priority, notes, mail to, etc.

Resolve a bug: When the bug is fixed, click Resolve, specify the resolution status, build, resolved date, and assign it to the tester.

Generally speaking, an ideal bug status is “Resolved”. As for other solutions, we will talk about them later.

Close a bug: Once the bug is solved, it will be assigned to the one who reported it. Then testers will test whether the bug is actually fixed. If accepted, the bug can be closed. You can click the Close button in Actions of bug list, or click the bug and close it.

Edit a bug: You can write a note for the bug closed.

Copy a bug: Copy and create a bug to make changes on this basis.