Approvals and SLAs
Two controls that put a process around a task: an approval, which holds work back until someone signs off, and an SLA, which puts a clock on a response.
Both are configured per project, and both need the Pro plan to set up.
Approvals
An approval rule says: before a task can move into this state, it needs this many sign-offs.
Set them up in project settings, then Approvals, then New rule:
- State: the state the rule guards. One rule per state, so a state cannot have two competing rules.
- Required approvers: how many approvals are needed. At least one.
- Allowed approvers: the people who may approve. Leave it empty and any project admin can.
Approving
A task covered by a rule shows an Approvals block, with how many of the needed approvals it has, and Approve and Reject buttons. You can withdraw your own vote afterwards.
Who may vote:
- If the rule names allowed approvers, only those people, whatever their project role.
- If it does not, project admins only.
There is nothing stopping you approving your own task. The rule counts approvals; it does not check that the approver is not the person who asked. If sign-off has to come from someone else, name the approvers explicitly rather than leaving the list empty.
What an approval actually stops
A task that does not have its approvals cannot be moved into the guarded state. The move is refused and says how many approvals are needed and how many it has.
Be clear about the limits of that, because it decides whether an approval is the right tool:
- It guards one move, not the task. Everything else, editing, commenting, reassigning, moving to any other state, is unaffected.
- It is not a permission. It gates a transition for everyone, including admins, rather than restricting who may do what. For that, use roles.
- Not every path that changes a state goes through it. The task's own state control is checked. Bulk editing many tasks at once, and automated paths such as intake handling and auto-close, write the state directly. So an approval is a strong signal in the normal flow, and not a wall around the data. If a transition genuinely must never happen without a sign-off, do not rely on this alone.
- Approvals are not reset. Once a task has them, it keeps them. If it leaves the state and comes back later, the old approvals still count.
Voting records no activity entry and notifies nobody, so if an approval is blocking someone, tell them.
SLA policies
An SLA policy puts a target on two things: how long until someone responds, and how long until the task is resolved.
Set them up in project settings, then SLAs, then New policy:
- Name.
- Priority filter and state group filter, so a policy can apply to urgent tasks only, or to everything.
- First response (minutes) and Resolution (minutes).
- Pause SLA while task is in backlog, which is on by default.
Every enabled policy whose filters match a task applies to it. There is no first-match rule, so a task can be under two policies at once and shows both.
What the clock measures
This is the part that surprises people, so it is worth being exact.
The clock starts when the task was created. Not when it was assigned, not when it entered a state, not when the policy was written. A consequence: a policy created today applies to tasks that already exist, and an old task can be past its target the moment you save the policy.
It is wall-clock time. There are no business hours, no working days and no holidays. A 480-minute target is eight real hours, including the night and the weekend.
First response means the first comment by somebody other than the person who created the task. A state change is not a response, and neither is the reporter commenting on their own task.
Resolution means the task reaching a completed state. A cancelled task is not resolved.
What you see
On the task, a block shows the policy and a chip for each target:
| Chip | Meaning |
|---|---|
| Met | The response or resolution happened before the target |
| "2h left" | Still running, with the time remaining |
| Late | It happened, but after the target |
| Breached | It has not happened and the target has passed |
That task block is the only place SLA state appears. There is no breach list, no dashboard, no board badge, no filter and no notification. Nothing tells you a breach happened; you see it when you look at the task.
So an SLA here is a clock you can read on the work, not an alerting system. If you need to be told, that is not something this can do for you today.
About "pause"
Pausing is narrower than it sounds. While a task sits in a paused state group, a breach is not declared. The deadline does not move. The time spent paused still counts, so a task can come out of the backlog already overdue.
Read the switch as "do not flag this while it is in the backlog", not as "stop the clock".
Timing
A background scan refreshes SLA state every few minutes, so a chip can be a little behind the real clock.
What happens after a downgrade
Worth planning for, because it is not obvious: existing rules and policies keep working. Approvals keep blocking transitions, and SLAs keep evaluating. What goes away is the settings page, which sits behind the plan gate.
A workspace that drops below Pro can therefore be left with an approval rule it cannot delete from the interface. If you are downgrading and you have rules you do not want, remove them first.
Who can do what
| Action | Needs |
|---|---|
| See a task's approvals and SLA | Any project member, guests included |
| Approve or reject | Being an allowed approver, or a project admin when no list is set |
| Create or delete rules and policies | Project admin |
| Create either at all | The Pro plan |
Troubleshooting
| What you see | What it means |
|---|---|
| "Approvals required before transitioning to this state" | The target state is guarded and the approvals are not in yet. |
| "You are not an allowed approver for this rule" | The rule names its approvers and you are not one. If the list is empty, only project admins can vote. |
| "Approval rule already exists for this state" | One rule per state. Delete the old one first. |
| Approve and Reject are shown but voting fails | The rule has no allowed approvers, so only project admins can vote. |
| "No available state" when making a rule | Every state in the project already has a rule. |
| A brand new policy says Breached | The clock runs from when each task was created, so existing tasks can already be past a new target. |
| A target was missed overnight | SLA targets are wall-clock. There are no business hours. |
| First response says nothing happened, but there are comments | Only a comment from someone other than the task's creator counts. |
| A paused task came back already overdue | Pausing suppresses the breach, it does not move the deadline. |
| You cannot find the settings page | It needs Pro. Existing rules stay in force. |
Related
- Tasks: states and what moving between them does.
- Custom fields and templates: shaping the task itself.
- Enterprise, SCIM and governance: roles, which are the real permission control.