Introduction
The Ticket Activity section in Visp.net Service Desk provides a chronological audit trail of actions performed on a ticket. It helps users understand what changed, when it changed, who made the change, and how the ticket progressed over time.
Use Ticket Activity to:
- Review ticket history.
- Confirm when updates were made.
- Track status changes.
- Audit technician or staff actions.
- Investigate customer disputes or service delays.
- Understand related work across linked tickets.
- Reconstruct timelines for outages, escalations, or complex service requests.
A well-reviewed activity log gives teams the context needed to troubleshoot issues, validate work, and maintain accurate service records.
Prerequisites
Before using the Ticket Activity section, make sure you have:
- Access to Visp.net Service Desk.
- Permission to view ticket details.
- The correct ticket opened.
- A basic understanding of the ticket workflow, including statuses, assignments, tasks, and linked tickets.
- Awareness of your organization’s configured system time zone.
- Ticket IDs or related subscriber information if you need to cross-reference activity across multiple records.
1. Open the Ticket Activity Section
To review ticket activity:
- Log in to Visp.net.
- Open Service Desk.
- Search for and open the ticket you want to review.
- Locate the Ticket Activity section on the ticket.
- Click the external link icon, if available, to open the full Ticket Activity window.
Opening the dedicated activity window gives you a clearer view of the ticket history and may provide additional options such as searching or including linked ticket logs.
2. Understand the Ticket Activity Columns
The Ticket Activity log is organized into columns that describe each recorded event.
Date Added
- Shows the date and time when the activity was logged.
- Helps establish the sequence of events.
- Example format may appear similar to:
- Jul 13, 2025 12:08 PM
Use this column to determine when actions occurred, such as ticket creation, status changes, task updates, or linked ticket changes.
Action
- Shows the type of activity performed.
- Common values may include:
- ADD — a new item, note, task, attachment, or relationship was added.
- CHANGE — an existing field, status, assignment, or task was modified.
Use this column to quickly understand the type of event recorded.
Details
- Provides a short description of what changed.
- May include information such as:
- Ticket links added.
- Tasks updated.
- Status changes.
- Assignment changes.
- Notes or comments added.
- Field values changed.
This column contains the main context for the activity entry.
User
- Identifies the user who performed the action.
- Useful for accountability, follow-up, and audit review.
If an action appears unexpected, use the User column to identify who made the change and when it occurred.
3. Read the Activity Log Chronologically
Ticket activity is commonly displayed with the most recent activity at the top.
To understand the ticket history:
- Start with the most recent entry to understand the latest update.
- Read downward to move backward through time.
- Identify key changes, such as:
- Ticket creation.
- Assignment updates.
- Status changes.
- Task completion.
- Attachment uploads.
- Linked ticket activity.
- Resolution or closure.
- Compare related entries to understand the full sequence of events.
For a complete timeline, continue reading until you reach the earliest activity entries.
4. Identify Key Ticket Events
When reviewing Ticket Activity, focus on events that explain how the ticket progressed.
Important events to look for include:
-
Ticket creation
- Confirms when the issue or request entered the system.
-
Assignment changes
- Shows when the ticket was assigned or reassigned.
-
Status changes
- Tracks movement from statuses such as Open, Pending, Resolved, or Closed.
-
Task updates
- Indicates which work items were completed and when.
-
Attachment uploads
- Confirms when supporting documents, photos, or files were added.
-
Linked ticket changes
- Shows when the ticket was connected to parent, child, or merged tickets.
-
Resolution or closure
- Identifies when the ticket was finalized.
These key events are especially useful when troubleshooting delays, validating service work, or reviewing customer communications.
5. Use Dates to Backtrack Ticket History
Dates and timestamps are essential for reconstructing what happened on a ticket.
To backtrack effectively:
- Identify the date of the customer report or service request.
- Compare it with the ticket creation date.
- Review when the ticket was assigned.
- Check when major updates were added.
- Confirm when tasks were completed.
- Review when the ticket was resolved or closed.
Use this process to answer questions such as:
- When did the customer first report the issue?
- When was the ticket created?
- How long did it take to assign the ticket?
- When did the technician update the ticket?
- When was service restored?
- When was the ticket closed?
6. Use the Search Bar to Find Specific Activity
The Ticket Activity window may include a search bar.
Use the search bar to locate specific entries by searching for:
- Dates
- Ticket numbers
- User names
- Status names
- Task names
- Keywords from notes or details
- Linked ticket IDs
- Action types such as ADD or CHANGE
Examples of useful searches:
- Resolved
- Closed
- Assigned
- Linked
- Attachment
- Jul 13
- Ticket #2241303
- Technician name
Searching helps narrow the log when a ticket has a long activity history.
7. Use Service Desk List View Filters for Broader Date Searches
If you need to search across multiple tickets rather than one activity log, use the Service Desk List View.
The List View may provide broader filtering options, such as:
- Date range
- Ticket status
- Assignee
- Subscriber
- Ticket type
- Priority
- Created date
- Updated date
Use List View filters when you need to:
- Find all tickets created during a certain period.
- Review tickets updated on a specific day.
- Investigate outage-related tickets.
- Locate tickets resolved during a billing or reporting period.
- Narrow down tickets before reviewing individual activity logs.
After filtering in List View, open the relevant tickets and review their individual Ticket Activity logs.
8. Include Linked Ticket Logs When Needed
For complex issues, enable Include Linked Tickets Logs if the option is available in the Ticket Activity window.
This option allows the activity log to include events from related tickets.
When to include linked ticket logs
Enable linked ticket logs when reviewing:
- Outages
- Emergency incidents
- Parent-child ticket structures
- Multi-phase installations
- Escalated support cases
- Merged or duplicate tickets
- Projects involving multiple related tickets
- Tickets with dependencies across teams
Benefits of including linked logs
- Provides a more complete timeline.
- Shows activity across related tickets.
- Helps identify dependencies or bottlenecks.
- Improves root-cause analysis.
- Supports post-incident reviews.
- Creates a more complete audit trail.
For example, if a parent outage ticket is linked to multiple customer child tickets, including linked logs can help show how the outage and customer reports progressed together.
9. Cross-Reference Activity with External Events
Ticket Activity is most useful when compared with related operational or customer information.
Cross-reference activity entries with:
- Customer calls or emails.
- Technician dispatch records.
- Network monitoring alerts.
- Outage start and restoration times.
- Appointment schedules.
- Billing events.
- Equipment replacement records.
- Internal escalation notes.
This helps create a complete and accurate timeline.
Example:
- If a customer reported an issue at 9:00 AM, check whether the ticket was created shortly afterward, when it was assigned, and when the first technician update was added.
10. Interpret Dates and Times Carefully
Accurate date interpretation is critical when reviewing ticket history.
Check the full timestamp
- Review both the date and the time.
- Do not rely on the date alone.
- Multiple important updates may occur on the same day.
Confirm the year
- Always verify the year, especially for older tickets.
- This is important when reviewing recurring issues or long-running service histories.
Be aware of the system time zone
- Ticket timestamps are based on the system’s configured time zone.
- If your team works across multiple regions, confirm how timestamps are displayed.
- Avoid assuming timestamps reflect your local time unless verified.
Use a consistent interpretation standard
Teams should use the same approach when reading ticket dates to avoid confusion during audits, escalations, or outage reviews.
11. Use Ticket Activity for Auditing and Accountability
The Ticket Activity log can support internal audits and quality control.
Use it to verify:
- Who changed the ticket status.
- When the ticket was assigned.
- Whether required tasks were completed.
- Whether attachments were uploaded.
- When customer-facing updates may have occurred.
- Whether linked ticket relationships were added.
- When the ticket was resolved or closed.
This is especially helpful when reviewing:
- Missed appointments.
- SLA or response-time concerns.
- Customer disputes.
- Reopened tickets.
- Escalated support cases.
- Completed field work.
- Billing-related service requests.
12. Follow Best Practices When Reviewing Ticket Activity
To get the most value from Ticket Activity, follow these best practices:
Start with the business question
Before reviewing the log, define what you need to know.
Examples:
- Why was the ticket closed?
- When was the technician assigned?
- Was the customer contacted?
- Was the issue part of an outage?
- Did all required tasks get completed?
Review key timestamps first
Focus on:
- Creation time
- Assignment time
- First update
- Status changes
- Resolution time
- Closure time
Look for gaps in activity
Identify long periods with no updates, especially between:
- Ticket creation and assignment.
- Assignment and technician action.
- Technician update and resolution.
- Resolution and closure.
Use linked logs for complex cases
If the ticket is part of a larger issue, include linked ticket logs to avoid missing related activity.
Document findings when necessary
If you identify important information during review, add a clear note to the ticket or follow your organization’s documentation process.
Avoid assumptions
Use activity entries as evidence, but confirm unclear situations with related notes, messages, attachments, or user follow-up.
Conclusion
The Ticket Activity section in Visp.net Service Desk provides a detailed history of ticket actions, including when changes occurred, what changed, and who made each update. By understanding the activity columns, reading entries chronologically, using timestamps carefully, searching for key events, and including linked ticket logs when appropriate, teams can reconstruct accurate ticket timelines and make better operational decisions.
Consistent use of Ticket Activity improves troubleshooting, accountability, outage reviews, customer communication, and service desk reporting.