Workflow

How to Manage Ticket Statuses

Verified end to end. A disposable status was created, loaded, renamed, deleted, and confirmed absent from the status list endpoint.

Evidence Summary

Workflow run
ticket-status-crud-20260519T142644Z
Route
/tickets/apoio/status
Status id
6
Final state
Disposable status deleted and absent from DT_Select_tickets_status.

Ticket status CRUD workflow diagram

Create or Edit

  1. Open Tickets, Support Files, then Status.
  2. Click Add Status to open the modal.
  3. Fill required Name.
  4. Choose the status type. The verified disposable row used normal, displayed as Standard.
  5. Use Active, Can Chosen, Closed Can Reopen, and Ask Time to control ticket workflow behavior.
  6. Click Save.

Create and update both submit createUpdateTikStatus with the serialized status form. The verified create used status_name=AI st 142644, status_type=normal, status_active=1, status_can_chosen=1, status_closed_can_reopen=1, and ask_time=1. It returned {"success":true,"id":6}.

Edit loads a row with loadTikStatus. The verified update used status_id=6 and status_name=AI st edit 142644, returning {"success":true,"id":"6"}.

Delete

  1. Click the delete action on the status row.
  2. Confirm the prompt.

Delete calls deleteTikStatus with id=6. The response returned {"success":true}. A final DT_Select_tickets_status call confirmed AI st edit 142644 no longer existed.

Artifacts