Tickets

A ticket is a unit of maintenance work — something that needs attention on a device or group. The Tickets screen (in the Operations section of the sidebar) is where you track and resolve them.

Where tickets come from

Tickets are created two ways, and you don’t have to file them by hand:

From alerts — when a device crosses a threshold, the resulting alert becomes a ticket to work (see Alerts & thresholds).
From the AI agent — when the analysis agent spots a developing problem or anomaly, it raises a ticket on its own (see AI analysis).

View your tickets

Open Tickets to see the list. You can change the layout and filter it:

Views (table / swimlanes) — a flat table, or swimlanes grouped by status.
Saved view tabs — All, Mine, Critical & High, Unassigned, Overdue, or Resolved.

A stats strip at the top summarizes how many tickets are open, in progress, overdue, and so on. Select a ticket to open its detail.

The ticket lifecycle

A ticket moves through a set of statuses as it’s worked:

Status	Meaning
Open	New, not yet started.
In Progress	Someone is actively working it.
On Hold	Paused for now.
Pending Parts	Waiting on parts or supplies.
Resolved	The fix is done.
Closed	Verified and finished.
Cancelled	No longer needed.

Work a ticket

On a ticket’s detail screen you can:

Assign it to the right person.
Move its Status along as the work progresses (for example Open → In Progress → Resolved → Closed).
Adjust its Severity, Priority, and Category so it sorts correctly in everyone’s views.
Record what you did in the Notes, and track effort and cost.