ITAM / Asset Tickets
Comments & Activity
Keep Sophie in the loop on her keyboard replacement through comments, and use Activity to see every status change Carlos made.
Real-world scenario
Sophie Park · Software Engineer at Bluewave Labs
Sophie checks her keyboard ticket Thursday afternoon. Carlos's comment says the keyboard arrived; she replies "Installed. works great" so he can close the ticket without a Slack ping.
Before you begin
- Access to the ticket (creator, assignee, or admin)
Overview
Comments are for human conversation; Activity is the system audit log. Together they replace scattered Slack threads on tickets like Sophie's keyboard replacement.
Activity timeline
- 1
Switch to the Activity tab
See chronological events: created, priority changed, assigned, status updates.
- 2
Review the audit trail
Each entry shows actor, action, and timestamp, useful when Maya asks who approved spend.
Notifications
Example thread
Sophie's keyboard ticket. comment + activity
Comments
- Carlos (Wed): MX Keys ordered. ETA Thursday
- Carlos (Thu): Keyboard at front desk Austin 3F
- Sophie (Thu): Installed. works great
Activity (selected)
- Mon 9:00. Sophie created ticket (OPEN, MEDIUM)
- Mon 9:30. Carlos changed priority to HIGH
- Mon 10:00. Carlos assigned to self; status → INPROGRESS
- Fri 15:00. Carlos status → RESOLVED → CLOSED
Related articles
Comments
Open the ticket detail view
Navigate to Sophie's keyboard ticket from the list or a notification link.
Go to the Comments tab
Read existing thread. Sophie's original description may appear as the first entry.
Add a comment
Carlos posts updates: "Ordered Logitech MX Keys. tracking #1Z999..." Sophie replies when it arrives.
Submit
Comments are timestamped and visible to everyone with ticket access.