Status & lifecycle#
Every node has a status: where the specification stands in authoring and review. The same status means the same thing in every project.
Status is not the test result or whether work is implemented. Those stay on test results and (later) a separate progress field.
States#
Requirements, tests, and risks share Draft, In review, Approved, and Obsolete. Customer requirements also have Partly approved and Rejected.
Internal requirement layers (system, software, hardware, mechanics) use the shorter set. Change a type's layer in Settings → Metamodel → Types & layers to pick the matching set.
On a node#
Open a node. The status field shows what the current state means and which states you can move to next. States that are not allowed from the current one are greyed out, for example a draft cannot jump straight to Approved. If a workspace process rule requires a field in the new state, the sidebar tells you before you save.
On the canvas card, the arrow next to the status moves the node one step along the main path, for example from Draft to In review.
Lifecycle on the field opens the state machine for that type.
Project overview#
Settings → Metamodel → Status & lifecycle shows the state machine as a diagram, with the meaning of each state, the allowed next steps, and the process rules that apply in each state.
Process rules are authored in Processes, not in the metamodel. The lifecycle page only shows the published rules.
Which transitions are allowed and why is explained in Metamodel.