Activity Timeline

Every meaningful change to a ticket is recorded as an event and displayed in the Activity timeline on the ticket detail page. This timeline provides a complete, chronological history of who did what and when – useful for context, accountability, and compliance.

Where to find it

  1. Open any ticket from the ticket list.
  2. In the left column of the ticket detail page, scroll below the description card.
  3. The Activity timeline shows all events in chronological order, oldest first.

Each event displays as a single entry with a colored dot indicator, a description of what changed, and a timestamp.


Event types and indicators

Each event type has a distinct colored dot so you can scan the timeline quickly:

EventDot colorWhat it shows
CreatedGreenThe ticket was created. Shows who created it.
Status ChangedBlueThe ticket’s status was updated. Shows the old status and the new status (e.g. Open to In Progress).
Priority ChangedOrangeThe ticket’s priority was updated. Shows the old priority and the new priority (e.g. Medium to Urgent).
AssignedPurpleAn agent was assigned to the ticket. Shows the agent’s name.
UnassignedPurpleAn agent was removed from the ticket. Shows the agent’s name.
Tag AddedA tag was added to the ticket. Shows the tag name.
Tag RemovedA tag was removed from the ticket. Shows the tag name.
SLA BreachedRedAn SLA deadline was missed. Shows which target was breached (first response or resolution).

Reading value transitions

For events that represent a change from one state to another – such as status changes and priority changes – the timeline entry displays the transition as old value to new value. For example:

  • Status Changed: Open to In Progress
  • Priority Changed: Medium to Urgent

This makes it easy to understand exactly what changed without needing to compare snapshots.


Actor attribution

Every event records who performed the action:

ActorDescription
AgentA support agent made the change through the UI. The agent’s name is displayed.
CustomerThe customer triggered the event, such as by replying through the portal.
SystemAuxilium itself triggered the event automatically, such as SLA breach detection.
System events
System-generated events like SLA breaches are triggered by background processes, not by a human action. They appear in the timeline with a system attribution so you can distinguish automated events from manual ones.

Timestamps

Each event includes a timestamp showing exactly when it occurred. Timestamps appear on the right side of each timeline entry. The combination of event type, actor, and timestamp gives you a precise record of every change.


Immutability

The activity timeline is append-only. Events cannot be edited or removed. This guarantees that:

  • Every state transition is permanently recorded.
  • The full history of a ticket can be reconstructed at any point.
  • Compliance and audit requirements are met without additional tooling.