Reprinted from: http://www.zentao.net/book/zentaopmshelp/64.html
The previous article described one of the simplest ways to use Zen trails, using only Zen Trails for project task management. The test function of Zen trails can also be used independently. This approach is ideal for use by test teams. The most basic process of the bug in Zen Road is that the tester puts the bug----developer to fix the bug, and the tester verifies the shutdown.
Let's show you how to use it. First, create a product
Before using the bug management feature, you need to create the product first. Zen Road design concept is that the bug is mainly attached to the product concept below, we will explain in detail the relationship between the product and the project.
When adding a product, you need to set the product name, code, and several responsible information.
Second, the proposed bug
With the product, we can create the bug.
When creating a bug, the required fields are basic information that affects the version, bug title, and repro steps. Project, related products, requirements can be ignored. When creating a bug, you can assign it directly to a person to process it. If it's not clear, you can leave it blank.
third, solve the bug
When a bug is assigned to a developer, he can verify that the bug is resolved.
2.1 Find a bug that needs to be handled by various tags and search criteria
Before you can make a bug, you need to find a bug that you need to handle. Zen Road provides a variety of search methods, such as assigned to me, can list all the bugs I need to deal with.
2.2 Fix bugs
The developer solves the bug, chooses the solution, and generally the effective solution to the bug is "resolved". Detailed solutions, which we will describe in detail in the following articles. Four, close the bug
When the developer resolves the bug, the bug is reassigned to the creator header of the bug. The tester can then verify that the bug has been fixed. If the validation passes, you can close the bug.