Deployments
A deployment is a release you are planning or running: what it is, where it goes, who has approved it, and what is left to do. Find them under Deployments.
What a deployment has
Section titled “What a deployment has”| Part | What it is |
|---|---|
| Name, Description | What is being released. |
| Environment | development, staging or production. |
| Status | draft, pending_approval, approved, in_progress, completed or failed. |
| Scheduled for | When it should happen. Leave it empty until a time is agreed. |
| Checklist | Up to 100 items. Each can be ticked off (with who and when), link a ticket, and carry its own approvals. |
| Approvals | People who approve the release: each pending, approved or rejected, with a comment. |
| Tickets | Linked tickets as people say them, such as JIRA-123 or INC-9, with a title and a link. |
Duplicating
Section titled “Duplicating”Duplicate starts the next release from the last one: the same checklist, approvals and tickets, with everything unticked.
Who can do what
Section titled “Who can do what”Owners, Admins and Operators create and change deployments. Responders can update them (for example tick items or record an approval). Viewers can only look. Deployments belong to the whole organization, not to a client.