approval.* events
The life of an approval request: an artefact put up for approval, each approver's verdict, the outcome the verdicts settle, a request taken back, a request that ran past its time, and a change to how a project decides a kind of approval.
The life of an approval request: an artefact put up for approval, each approver's verdict, the outcome the verdicts settle, a request taken back, a request that ran past its time, and a change to how a project decides a kind of approval. A client dashboard that shows what waits for sign-off, a Slack or Teams relay that tells approvers, and an audit trail of who approved what subscribe to this family.
Every event in the family is scoped to the project, so project_id in the envelope is always set and an endpoint confined to one project receives only that project's approvals. The payloads carry the ids, the artefact's reference and what the move itself carries, never the artefact or the verdicts in full: read the approvals endpoint for the request with its decisions, and the artefact's own family (requirement.status_changed and its siblings) for the status move an approval makes on the record.
Background
Required ability
Tokens subscribing to approval.* events need approval:view at mint time.
Events
approval.requestedAn artefact is put up for approval.approval.decidedOne approver gives a verdict.approval.approvedA request carries.approval.rejectedAn approver rejects the request.approval.changes_requestedAn approver asks for changes.approval.withdrawnAn open request is taken back.approval.escalatedA pending request passes the time the policy allows.approval.policy_updatedA project changes how one kind of approval is decided.How is this guide?
Last updated on