Overview
The Ticket Detail view provides a comprehensive snapshot of each support ticket, including metadata, priority, device context, internal notes, and lifecycle controls. IT staff can assess, update, and resolve issues efficiently through this centralized interface.
Before You Start
Required permissions: Admin or Staff role with ticket access
Supported platforms: Web-based Trio Console (Chrome, Edge, Safari)
Device type: Desktop or laptop
Network requirements: Stable internet connection with access to the Trio Console
Step 1: Open a Ticket Detail View
Navigate to Services → Ticketing System → Tickets
Click any Ticket ID in the table to open its detailed view
Expected result: The Ticket Detail screen opens, showing summary, priority, device info, and other metadata
Step 2: Review Summary and Attachments
View the ticket description, reporter name, and uploaded files (e.g., images, videos)
The request type (e.g., Hardware, Application) is shown as a label above the message
Expected result: Full context of the issue is visible with all attached evidence
Step 3: Add Internal Notes
Scroll to the Internal Notes section
Type context, updates, or troubleshooting steps (not visible to the user)
Press Enter or click outside the box to save
Expected result: Notes are timestamped and saved for team reference
Step 4: Change Ticket Priority
Click the Priority dropdown (e.g., Critical, High, Medium, Low)
Select the appropriate level based on urgency and impact
Expected result: The priority badge updates instantly
Step 5: Assign the Ticket
In the Assignee section:
Click Assign to me to self-assign
Or choose a team member from the dropdown
The ticket will now show the assignee's name and avatar
Expected result: The Assignment is saved, and the status may change toIn Progress
Step 6: Update Ticket Status
Click the current Ticket Status (e.g.,
Pending support) in the top-rightChoose a new status from the dropdown:
In progress
Pending info
Resolved
User pending
On hold
Canceled
Confirm the update if prompted
Expected result: Status is reflected across the system and in reports
Step 7: Review Reporter and Device Information
On the right-hand pane, view:
Reporter Name and email
Group, Job title, and Location
Associated device details (e.g., OS, model, serial number)
Expected result: You have full context for the user environment and configuration
Next Steps
Immediate actions:
Add notes after each update or contact
Ensure every ticket has an assignee and the correct priority
Related configurations:
Tag tickets to Asset entries
Automate status transitions via policies (if enabled)
Troubleshooting
Issue | Cause | Solution |
Status won’t update | No assignee set | Assign a ticket before changing the status |
Cannot save notes | Network timeout | Reconnect and retry |
Device info missing | Device not linked | Confirm the user enrolled through Fleet |
If you have more questions regarding ticket details, please contact the Trio team.