Workflow

How to Manage Ticket Priorities

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

Evidence Summary

Workflow run
ticket-priorities-crud-20260519T142035Z
Route
/tickets/apoio/priorities
Priority id
5
Final state
Disposable priority deleted and absent from DT_Select_tickets_priorities.

Ticket priorities CRUD workflow diagram

Create or Edit

  1. Open Tickets, Support Files, then Priorities.
  2. Click Add Priority to open the modal.
  3. Fill required Name.
  4. Use Active to enable or disable the priority.
  5. Optionally configure font weight, text color, background color, and icon.
  6. Click Save.

Create and update both submit createUpdateTikPriority with the serialized priority form. The verified create used priority_name=AI pr 142035, priority_active=1, priority_style_fontweight=normal, and empty icon/color fields. It returned {"success":true,"id":5}.

Edit loads a row with loadTikPriority. The verified update used priority_id=5 and priority_name=AI pr edit 142035, returning {"success":true,"id":"5"}.

Delete

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

Delete calls deleteTikPriority with id=5. The response returned {"success":true}. A final DT_Select_tickets_priorities call confirmed AI pr edit 142035 no longer existed.

Artifacts