change_request.* events
The life of a project's change requests: a request raised, its words or impact changed, moved along its lifecycle by hand or by the approval engine, read by Heimdall for its impact, put back to an earlier version and deleted.
The life of a project's change requests: a request raised, its words or impact changed, moved along its lifecycle by hand or by the approval engine, read by Heimdall for its impact, put back to an earlier version and deleted. A client portal that shows what was asked for and what it costs, a planning tool that moves dates when a change is approved, and an audit trail of what changed after the scope was signed 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 events. The payloads are thin on purpose: the ids, the reference, the reason and what the move itself carries, never the impact in full. Read the change requests endpoint for the record with its impact and versions, and the approval.* family for the request behind an approval or a rejection.
Background
Required ability
Tokens subscribing to change_request.* events need change-request:view at mint time.
Events
change_request.createdA change request is raised.change_request.updatedA change request's fields change.change_request.status_changedA change request moves between its states.change_request.analysedHeimdall read a change request against its baseline.change_request.restoredAn earlier version of a change request is put back.change_request.deletedA change request that was never agreed is deleted.How is this guide?
Last updated on