Sanplex tracks story changes using two primary fields: the story status field and the story development phase field. Let's look at how these two fields operate.

图1

I. Story statuses

The story status field includes five statuses: Draft, Reviewing, Active, Changing, and Closed. The corresponding workflow actions are Create, Review, Change, Close, and Activate. The status transition flow is illustrated below:

图2

图3

II. Story phases

Stories also have a phase field to describe their current stage in the development process.

• The phases of a standard story include: Unstarted, Planned, Project Initiated, Designing, Developing, Developed, Testing, Tested, Accepted, Acceptance Failed, Released, and Closed.
• The phases of business stories, user stories, and parent stories include: Unstarted, Planned, Project Initiated, Developing, Delivering, Delivered, and Closed.

图4

How does the development phase of a story change? One approach is to manually modify the phase through the edit operation. However, we highly recommend an alternative automated approach. When creating tasks, you should carefully assign the task type, such as design, development, or testing. Sanplex will automatically calculate the story's development phase based on the progress of these different task types. The rules are as follows:

1. If the story is not linked to any project or plan, the phase is Unstarted.

2. If the story is linked to a plan but not yet linked to a project, the phase is Planned.

3. If the story is linked to a project but no tasks have started, the phase is Project Initiated.

4. If the story is linked to a project and tasks have been broken down:

   • If a design task is in progress, and all development and testing tasks have not started, the phase is Designing.
   • If all design tasks are completed, and all development and testing tasks have not started, the phase is Designed.
   • If a development task is in progress, and all testing tasks have not started, the phase is Developing.
   • If all development tasks are completed, and all testing tasks have not started, the phase is Developed.
   • If a testing task is in progress, the phase is Testing.
   • If all testing tasks are finished, but some development tasks are not finished, the phase remains Testing.
   • If all testing tasks and all development tasks are finished, the phase is Tested.

5. The Accepted phase requires manual confirmation by the Product Manager. After confirmation, the phase changes to Accepted or Acceptance Failed.

6. When a story is linked to a release and the release status becomes Released, the story's phase automatically becomes Released.

7. When a story is manually closed, its phase becomes Closed.

Phase calculation rules for business stories, user stories, and parent stories:

The phases of business stories, user stories, and parent stories cannot be manually modified. Sanplex automatically calculates their phases based on the phase changes of the story itself and its child stories. The rules are as follows:

1. If the business/user/parent story is not linked to any plan or project, and none of its child stories are linked to a plan or project, the phase is Unstarted.
2. If the business/user/parent story or its child stories are linked to a plan, but neither is linked to a project, the phase is Planned.
3. If the business/user/parent story or its child stories are linked to a project, and the child stories have not started any tasks, the phase is Project Initiated.
4. If any child story has started a task, the phase of the business/user/parent story becomes Developing.
5. If any child story is linked to a release or is completed and closed, the phase of the business/user/parent story becomes Delivering.
6. If all child stories are linked to a release or are completed and closed, the phase of the business/user/parent story becomes Delivered.
7. When a business/user/parent story is manually closed, its phase becomes Closed.