- 1 Introduction
- 2 How to Install ZenTao
- 2.1 Choose the best installation
- 2.2 ZenTao Cloud
- 2.3 One-click Installation for Windows
- 2.4 One-click Installation for Linux
- 2.5 Installation with Lampp
- 2.6 Source Code Installation (for all Systems)
- 2.7 Set up Virtualbox for ZenTao
- 2.8 Softaculous service
- 3 Upgrade ZenTao
- 3.1 Upgrade ZenTao
- 3.2 Upgrade by source code (for all systems)
- 3.3 Upgrade for one-click installation for Windows (xampp)
- 3.4 Upgrade for one-click installation package for Linux
- 4 Users and Groups
- 5 Simple Application
- 5.1 Project and Task Management
- 5.2 Bug Management
- 5.3 Product Management
- 5.4 Individual Task Management
- 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 Stories
- 6.9 Story Breakdown
- 6.10 Report a Bug
- 6.11 Manage Contacts
- 6.12 Customization
- 7 Advanced Application
- 7.1 Workflow
- 7.1.1 ZenTao Workflow
- 7.2 Personal management
- 7.3 For 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 Story Status
- 7.3.6 Notes for Writing a Story
- 7.3.7 Product Modules
- 7.3.8 Release Plan
- 7.3.9 Create a Release
- 7.3.10 Roadmap
- 7.3.11 Manage Documents
- 7.3.12 Product Planning Meetings
- 7.3.13 Daily Scrum, Review and Retrospective Meetings
- 7.3.14 Story Reports
- 7.4 For Project Manager
- 7.4.1 Create a Project
- 7.4.2 Set up a Team
- 7.4.3 Confirm Stories
- 7.4.4 Story Breakdown
- 7.4.5 Daily Standup Meetings
- 7.4.6 Check Project Progress via Burndown Chart
- 7.4.7 Check Project Progress via Lists
- 7.4.8 Review and Retrospective Meetings
- 7.4.9 Basic reports on tasks
- 7.5 For Development Team
- 7.5.1 Project planning meeting and task breakdown
- 7.5.2 Claim tasks and update
- 7.5.3 Kanban and Tree Diagram
- 7.5.4 Create a Build
- 7.5.5 Test Task
- 7.5.6 Resolve a Bug
- 7.5.7 Manage Documents
- 7.5.8 Confirm Bugs
- 7.6 For QA Team
- 7.6.1 Bug Management
- 7.6.2 Report a Bug
- 7.6.3 Confim and Close a Bug
- 7.6.4 Activate a Bug
- 7.6.5 Locate a Bug
- 7.6.6 Test Cases
- 7.6.7 Create and Review Test Cases
- 7.6.8 Manage Test Tasks
- 7.6.9 Test Suites, Public Case Libs and Reports
- 7.6.10 Manage Test Tasks
- 7.6.11 Execute Cases and Report Bugs
- 7.6.12 Reports
- 8 Configuration
- 8.1 Maintain ZenTao
- 8.1.1 Initialize scripts
- 8.1.2 Back up ZenTao
- 8.1.3 Recover the Deleted
- 8.1.4 Update Burndown charts
- 8.1.5 ZenTao remote host
- 8.2 Deploy ZenTao
- 9 Custom Development
- 9.1 ZenTao customization
- 9.2 ZenTao Directory
- 9.3 Locate and Change Files
- 9.4 ZenTao 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 Web Editor
- 9.11 Packaging Standards of ZenTao 1.1
- 10 Other Relevant Issues
There are two fields in ZenTao to track the changes of stories. One is Story Status and the other one is Stages of development. Now, let’s take a look at the two fields in details.
1. Story Status
There are four types of Status, Draft, Active, Changed and Closed. The corresponding actions are Create, Change and Review, Close and Activate. The status flow is shown as below.
2. Story Development Stages
Stage is to describe the stage of an activc story in development. The stages include Wait, Planned, Pojected, Developing, Developed, Testing, Tested, Accepted and Released.
How does a story change in development?
One way is to change stage through editing. But the other way is preferred, which is to set the type of tasks, such as development and test, when creating stories. ZenTao will decide the stages according to the types of tasks. The rules are,
2.1 If stories are not linked to the projects or the plans, the stage will be “Wait”.
2.2 If stories are linked to plans but not to projects, it will be “Planned”.
2.3 If stories are linked to projects but not decomposed to tasks, it will be “Projected”.
2.4 If stories are linked to projects and decomposed to tasks:
If one of the development tasks is being done while all the test tasks have not yet begun, then it will be “Developing".
If all the development tasks are completed while all the test tasks have not yet been begun, then it will be “Developed”.
If one of the test tasks has been begun, then it will be “Testing”.
If all the test tasks are completed while some development tasks have not been completed, it will also be “Testing”.
If both the test tasks and development tasks are completed, it will be “Tested”.
2.5 The stage of Acceptance should be confirmed manually by the project manager.
2.6 If the stories are linked in Product->Release. It will be “Released”.
Notes for story which is linked to a multi-platform/branch product:
Take a multi-platform product as an example. A product has Andriod and IOS platforms.
- If the story is not linked to any project/plan, the story status is "Wait".
- If the story is linked to all platforms and its linked plans are linked to all platforms, the story status is "All Platforms: Planned". If the plan is linked to IOS, the story status is "IOS: Planned". If the story is linked to a specific platform, its status will be decided in the way mentioned above (How does a story change in development? ).
- The project is linked to a platform of the product. For example, the project is linked to IOS, and it is linked to the stories of all the platforms of the product it is linked to and the stories linked to IOS. The stories haven't been decomposed into tasks. Then, the status of a story that is linked to IOS is "Planned" and the story status of all the platforms that the product is linked to is "IOS: Planned". If the story status of all the platform that this story is linked to is "Planned", it will show "All Plaforms: Planned" and "IOS: Projected".
If a story is linked to two projects, one of which is linked to IOS and the other to all platforms of the product. Task breakdown is done yet. Then the status of this story is "All Platforms:Projected" and "IOS: Projected".
Edit Story Status in ZenTao 7.2.stable.
Click the title of a story and you will see the story detail page. Click Edit. On the right column of the page, you can change the status of the story, then click Save.
Go back to Product->Story, and you can see the status has been changed.