Product · Review & approval
Pre-review, formal review packages, and clear finalization
Formal review of stakeholder requirements is driven by stakeholder/stakeholder-group per requirement. System requirements use per-requirement reviewers (user or group). Review packages bundle selected requirements in a round with per-requirement status before the package can be finalized.
Overview
Pre-review, quick triage (yes/maybe/no) per user update; separate from the formal status.
Formal review package, created with description + list of stakeholder or system IDs; blocks double-active review for the same requirement.
Per-requirement status, each requirement gets a review status; ready to finalize when all have a decided status.
Finalization, sets the package to completed and runs batch fastställelse on requirements (including changelog); requires appropriate permissions.
Requirement specifications (separate flow)
Document-based review
For requirement specifications there is a dedicated flow: send version to named reviewers (users + groups), comments anchored to document/section/requirement, outcomes, and PDF protocols.