project.* events
The lifecycle of a project and its membership: creation, edits, status moves, archiving, restoring, deletion, and people joining or leaving it.
The lifecycle of a project and its membership: creation, edits, status moves, archiving, restoring, deletion, and people joining or leaving it. A project is the container every component, environment, epic, story, test, release and incident lives under, so these events are the ones a mirror of the registry subscribes to first.
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: ids plus what the transition itself carries, never a snapshot of the project. Read the projects endpoint for the record.
Arriving with project membership. Every event in the family is raised today except
project.member_removed, which is declared, documented and delivered the moment the project membership page lands; nothing about its shape will change. A webhook test-fire borrowsproject.created's shape with asyntheticmarker.
Background
Required ability
Tokens subscribing to project.* events need project:view at mint time, and project-member:view for the two project.member_* events.
Events
project.createdA project is created.project.updatedA project's own fields change.project.status_changedA project moves between lifecycle statuses.project.archivedA project is archived.project.restoredAn archived project is restored.project.deletedA project is deleted with everything under it.project.settings_changedOne or more of the project's settings change.project.member_addedA person gains a membership row on the project.project.member_removedA person's membership row on the project is removed.How is this guide?
Last updated on