Approval steps

Some work shouldn't go ahead until the right person says yes: a purchase over a limit, a new hire's equipment, time off. An approval step makes the ticket wait for that decision, then sends it on by itself.

Add one

In the editor's Stages layer, click a stage's name and choose + Add an approval step, or click a step and switch it from Work step to Approval. An approval is always the last step in its stage, and it shows in green on the canvas.

Then pick Who approves?

• A specific person: they get an Approve and a Reject button on the ticket.
• Anyone on a team: the first person on the team to decide settles it.
• Everyone on a team: it's approved once all of them approve. One reject rejects it.

After the decision

The decision is saved in a field (a Decision field with Approved and Rejected is added for you). Under After the decision, each rule says where the ticket goes: If Decision is Approved, go to Ordering. Add Approved and Rejected paths sets up both in one click, adding closing Approved and Rejected stages if you need them. To send rejected tickets back for changes, point Rejected at an earlier stage.

Deciding

When a ticket reaches the approval step, each approver gets a notice. On the ticket they see who it's waiting for, an optional note, and ✓ Approve and ✕ Reject. A note is saved on the ticket as an internal comment. With Everyone on a team, the ticket shows who has decided so far.

The stack's Owners and Managers can decide too, so a ticket never gets stuck when an approver is away.