- 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
When basic features are set, it’s time to create a build which is related to software configuration management. It is optional, but it is recommended that teams use build management.
A build is used to identify the test scope and make it easier for communications between the QA teams and the development teams, and to solve the problems such as build releases and bug fixing.
Since ZenTao has build management, can ZenTao be used to manage source code? Sorry, ZenTao cannot be used to do that, because it is a professional management to manage source code, and there is great open source software available to do it, such as Subversion and Git. You can deploy it according to your own needs. Builds in ZenTao are to make records.
1. The build workflow is as follows,
- The Dev teams have stories done or bugs resolved.
- A tag is created in Subversion or Git. Take ZenTao tag as an example,
- When a tag is created, a build can be created in ZenTao.
2. Create a build
Go to Project->Build and click Create.
Then you will the page below.
You need to create a build first. Once it is saved, link it to stories and bugs on the page of build details.
If there is no Link button on the detailed page of a build, contact the administrator to assign privileges by going to Company -> Group.
- Name. Teams should have their own management standards. For example, they can use product name_version number_status (stable, beta) _date to name builds.
- It can be different for builds due to different development languages. Some builds need to be adapted, while other builds only need source code. So you have to fill the SCM path or the file path for downloading according to the actual situations.
- In ZenTao, you need to create a build first and then link it to stories and bugs. Then the build is submitted to be tested after being linked, the testing scope will be defined.
- You can add notes, keynotes and so on in description for QA teams.