Product
1. Introduction of Sanplex features
1.1. Core Management Framework
1.1.1 Program
1.1.2 Project
1.1.3 Product
1.1.4 Execution
1.1.5 Management Models
1.2. Dashboard
1.2.1 Getting Started with Tutorials
1.2.2 Quick Add
1.2.3 Notification Center
1.2.4 Effort Tracking
1.2.5 Dashboard - Project and Execution
1.2.6 Dashboard - My Work, Contribution, and Recents
1.2.7 Dashboard - Approval
1.2.8 Contacts
1.3. Program
1.3.1 Program List
1.3.2 Program Kanban
1.3.3 Create Program
1.3.4 Create Sub-Programs
1.3.5 Project Charter Management
1.4. Product
1.4.1 Create Product
1.4.2 Manage Modules
1.4.3 Multi-Branch and Multi-Platform Management
1.4.4 Manage Plans
1.4.5 Manage Requirements
1.4.6 Requirement Reviews
1.4.7 Requirement Status and Phase
1.4.8 Create Releases
1.4.9 Track Progress
1.4.10 Business Requirements and Multi-Level Requirements
1.5. Project
1.5.1 Scrum Project
1.5.2. Waterfall Project
1.5.2.1 Manage Project Phases
1.5.2.2 Project Design
1.5.2.3 Project Matrix
1.5.2.4 Project Reports and Earned Value Management
1.5.2.5 Project Baselines
1.5.2.6 Project Change
1.5.3. Kanban Project
1.5.3.1 Set Up Kanban Projects
1.5.3.2 Configure Kanban Boards
1.5.3.3 Use Kanban Boards
1.5.4 Hybrid Agile Project
1.5.5 Hybrid Waterfall Project
1.5.6. Project Settings
1.5.6.1 Project Setup
1.5.6.2 Project Executions
1.5.6.3 Project Requirements
1.5.6.4 Project Builds
1.5.6.5 Project Tests
1.6. Admin Settings
1.6.1 Confluence Data Import
1.7. Workflow

Requirement Status and Phase

2026-08-17 12:03:59
Sanplex Content
159
Last edited by Jing WANG on 2026-08-17 12:04:38
Share links
Summary: Learn how Sanplex uses Status and Phase to track Requirement workflows, review transitions, development progress, and delivery progress.

Catalog

Sanplex uses two fields, Status and Phase, to track the workflow and development progress of Requirements.

Story list showing the Status and Phase columns highlighted. Example Status values include Reviewing, Draft, Activated, and Changing, while example Phase values include Planned, Waiting, and Closed.

I. Requirement Status

The Status field tracks the current workflow state of a Requirement. The main statuses are Draft, Reviewing, Activated, Changing, and Closed.

Depending on the current status, available workflow actions can include creating, submitting, reviewing, changing, closing, and activating a Requirement. The creation and review workflow is shown below.

Flowchart showing a Requirement moving from creation through Draft, reviewer assignment, review, Active, and Closed states, including direct submission, review rejection, clarification, and review withdrawal paths.

The change review workflow for an activated Requirement is shown below.

Flowchart showing an activated Requirement entering the change process and moving through Changing, reviewer assignment, review, Active after change, and Closed states, including direct submission, review rejection, clarification, and revoke-change paths.

II. Requirement Phase

The Phase field describes the current development or delivery phase of a Requirement.

For Development Requirements, the Phase field includes development-related phases such as:

Waiting, Planned, Initiated, Designing, Design Completed, Developing, Dev Completed, Testing, Test Completed, Accepted

Additional phases may be applied as the Requirement progresses through acceptance, release, or closure.

For Business Requirements, User Requirements, and parent Development Requirements, the Phase reflects their overall progress based on the Requirement itself and its child Requirements.

Edit Story page with the Phase field highlighted under Basic Info. The open dropdown shows Waiting, Planned, Initiated, Designing, Design Completed, Developing, Dev Completed, Testing, Test Completed, and Accepted.

1. How the Phase of a Development Requirement Changes

The Phase of a Development Requirement can be updated manually when applicable. However, Sanplex can also calculate the Phase automatically based on its links to Plans and Projects and the progress of related Tasks. When creating Tasks, assigning appropriate Task types such as Design, Development, and Testing enables Sanplex to determine the Requirement Phase according to the following rules:

  1. If a Development Requirement is not linked to a Project or Plan, its Phase is Waiting.
  2. If a Development Requirement is linked to a Plan but not yet linked to a Project, its Phase is Planned.
  3. If a Development Requirement is linked to a Project but no Task has started, its Phase is Initiated.
  4. If a Development Requirement is linked to a Project and related Tasks have been created:
    • If at least one 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 Design Completed.
    • If at least one 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 Dev Completed.
    • If at least one Testing Task is in progress, the Phase is Testing.
    • If all Testing Tasks are completed but some Development Tasks remain incomplete, the Phase remains Testing.
    • If all Testing and Development Tasks are completed, the Phase is Test Completed.
  5. Acceptance is confirmed manually by the product manager. Based on the acceptance result, the Requirement proceeds to Accepted or Acceptance Failed.
  6. If a Development Requirement is linked to a Release under Product > Release and the Release status changes to Released, the Requirement Phase becomes Released.
  7. If a Development Requirement is manually closed, its Phase becomes Closed.

2. Phase Rules for Business Requirements, User Requirements, and Parent Development Requirements

The Phase of Business Requirements, User Requirements, and parent Development Requirements is calculated automatically based on the Requirement itself and the progress of its child Requirements:

  1. If the Requirement itself and all of its child Requirements are not linked to a Plan or Project, its Phase is Waiting.
  2. If the Requirement itself or any of its child Requirements is linked to a Plan, and neither the Requirement nor any child Requirement is linked to a Project, its Phase is Planned.
  3. If the Requirement itself or any of its child Requirements is linked to a Project, and no child Requirement has started a Task, its Phase is Initiated.
  4. If any child Requirement has started a Task, the Phase becomes Developing.
  5. If any child Requirement is linked to a Release or has been completed and closed, the Phase becomes In Delivery.
  6. If all child Requirements are linked to a Release or have been completed and closed, the Phase becomes Delivered.
  7. If the Business Requirement, User Requirement, or parent Development Requirement is manually closed, its Phase becomes Closed.
Write a Comment
Comment will be posted after it is reviewed.