What needs approval
Every tool that creates or changes something waits for approval:
- Set review status (Code host)
- Create ticket (Issue tracker)
- Add comment (Issue tracker)
- Move ticket (Issue tracker)
- Update ticket fields (Issue tracker)
- Create sub-task (Issue tracker)
- Link tickets (Issue tracker)
- Contact Gunnie (Gunnie)
Routines work the same way: the developer notes, estimates and comments they propose, and the branch a build wants to push, all wait for approval.
What you see
Each waiting change shows what will happen and where, followed by the exact text: the comment, the developer note, the estimate, the ticket. Open Approvals in the control panel, read it, and choose Approve or Reject. Rejecting writes nothing.
Your assistant tells you when something waits for you, and can check the outcome afterwards.
How long a change waits
- A change your assistant asked for waits 15 minutes.
- A proposal from a routine waits 7 days, so it can wait for the next working day.
- After that it expires and nothing is written.
Who decides
The member who asked decides their own changes. An admin sees and decides every member’s changes as well; the change then runs as the member who asked, within that member’s role, and the record names who approved it.
Routine proposals go to the member who owns the routine. Admins can approve all proposals of one run at once, after a confirmation that lists every write.
Demo organisations
In a demo organisation, approving shows what would happen, but nothing is written to the real system.