- 1. Introduction
- 2.1 Choose the Right Installation
- 2.2 ZenTao Cloud
- 2.3 One-click Installation for Windows
- 2.4 One-click Installation for Linux
- 2.5 Lampp Installation in Linux
- 2.6 Source Code Installation (for all systems)
- 2.7 Source Code Installation for macOS
- 2.8 XAMPP-VM Installation for macOS
- 2.9 XAMPP Installation for macOS
- 2.10 Install ZenTao in Docker
- 2.11 Install httpd, Mariadb, PHP 7.2 in Cent OS 8
- 2.12 Softaculous Service
- 2.13 Install Ioncube
- 3. Update
- 4. Users and Groups
- 5. Quick Start
6. Basic Application
- 6.1 Basic Workflow
- 6.2 Agile and Scrum
- 6.3 ZenTao and Scrum
- 6.4 ZenTao Tutorial for Rookies
- 6.5 Create a Product
- 6.6 Create a Story
- 6.7 Create a Project
- 6.8 Confirm a Story
- 6.9 Decompose Stories into Tasks
- 6.10 Report a Bug
- 6.11 Manage Contacts
- 6.12 Customization
- 6.13 Import Excel, CSV Files
- 6.14 Document Management
- 6.15 Work Mode
- 6.16 Points
- 6.17 Required Field
- 6.18 Privileges
- 6.19 Annual Work Summary
7. Advanced Application
- 7.1.1 ZenTao Workflow
- 7.2. Individual management
7.3. Product Owner
- 7.3.1 Manage a Product
- 7.3.2 Manage a Product Line
- 7.3.3 Create and Review a Story
- 7.3.4 Change and Review a Story
- 7.3.5 Status and Phase
- 7.3.6 Story Writing
- 7.3.7 Product Module
- 7.3.8 Release Plan
- 7.3.9 Create a Release
- 7.3.10 Roadmap
- 7.3.11 Documents
- 7.3.12 Planning Meetings
- 7.3.13 Daily Scrum, Review and Retrospective Meetings
- 7.3.14 Story Reports
- 7.4. Scrum Master
- 7.5. Development Team
- 7.6. Test Team
- 7.1. Workflow
- 8.1. Maintain ZenTao
8.2. Deploy ZenTao
- 8.2.1 Guest Login
- 8.2.2 Email Notification
- 8.2.3 Set Super Admin
- 8.2.4 Static Access
- 8.2.5 Remove "zentao" from URL
- 8.2.6 Integrate SVN
- 8.2.7 Integrate Git
- 8.2.8 Integrate Webhook
- 8.2.9 Integrate Xuan.im
- 8.2.10 Integrate Zdoo
- 8.2.11 Integrate Third-Party Apps
- 8.2.12 Password-Free Login
- 8.2.13 Translation Add-on
- 8.2.14 Integrate Jenkins
- 8.2.15 Extension
- 8.2.16 Fix Weak Password
- 9.1 Introduction
- 9.2 Directory
- 9.3 Find Codes
- 9.4 Database Structure
- 9.5 Common Modules
- 9.6 Add Features to Menu
- 9.7 Set Privileges to Modules
- 9.8 Examples: modify language prompt
- 9.9 Examples: set priority when creating bugs
- 9.10 Extension Editor
- 9.11 Feature Limitation
- 9.12 ZenTao Packaging Standards 1.1
- 10. Misc
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 bugWhen a bug is assigned to a certain developer, he can confirm and solve the bug. How to find the assigned bugs? ZenTao provides a variety of search methods such as AssignedToMe, it lists all the bugs that need to be processed.
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.