Ticket Lifecycle
Statuses
submitted: new ticket awaiting verification.verified: accepted and ready for execution.in_progress: active implementation.waiting: waiting for reporter feedback/verification.blocked: blocked by missing data/dependency.closed: completed and closed.
Transition rules
- Only developers can move global execution statuses.
- Standard users can edit tickets only while status is
submitted. - Closing transition requires at least one closure summary comment.
Closure summary requirement
Before switching ticket to closed, a developer must add a public comment with is_closure_summary=true.
If missing, API returns closure_summary_required.
Planning shortcut
When a developer plans a submitted ticket (assignee, plan date, estimate), it can auto-transition to verified.
Notifications
Reporter notifications are sent on key status changes and developer public comments.