Skip to main content

Ticket lifecycle v2: blockers and close-review

The ticketing docs now cover the expanded ticket lifecycle:

  • New Blocked status and blockers — managers, PMO/PM, and admins can create a blocker on an In-Progress ticket; the parent auto-unblocks when the blocker is closed and verified. See Tickets.
  • Close-review — every closed ticket now carries an Unverified / Verified / Rejected badge and an auto-assigned reviewer; rejecting prompts a relative ticket. See Reviewing a closed ticket.
  • New notifications — review requested, verified/rejected, and blocked/unblocked. See Notifications.
  • Backend contract — REVIEWER role, closedBadge/blockerId fields, POST /tickets/{id}/review and /blockers, and five new os.events types. See Backend Services.