Last updated: 2025-12-01

Source: https://support.freshdesk.com/support/solutions/articles/37589-viewing-ticket-activity-history

When a ticket is assigned, reassigned, or updated, you may want to review what has changed since it was created, whether automatically or manually.

For example:

  • Agents can track updates to fields, ownership, or status.
  • Admins can review the complete ticket history, including responses, field changes, and automation rules executed.
  • The Show Activities button on the ticket details page provides a comprehensive log of all activity on a ticket.
  • ``` Note:  If you signed up for Freshdesk before November 2025, the view activity page will be different. ```

    How to view ticket activities?

    To View Ticket Activities:

    1. Click on any ticket from Tickets. 2. In the Ticket Details page, click on the Activities button in the top right corner.

    In the normal view:

    You will only see the ticket description, all replies/notes, and CSAT survey responses (if enabled).

    When Activities is on:

    1. Replies/notes are collapsed. 2. A chronological list of ticket activities becomes visible. Each activity has a corresponding label and action description, such as SLA updated or Watcher added.

    What are the types of activities tracked?

    The Activities log captures the following:

  • Changes to default fields (Type, Status, Priority, Group, Agent, Product, Source)
  • Changes to non-textual custom fields (Dropdown, Checkbox, Number, Date, Decimal, Dependent fields)
  • Changes to textual custom fields (single-line and multi-line text fields — timestamp only)
  • Edits to ticket subject or description (timestamp only)
  • Adding/removing tags
  • Adding watchers
  • Adding CCs to tickets
  • Splitting/merging tickets
  • Deleting tickets
  • Marking tickets as spam
  • Restoring spam/trashed tickets
  • Editing or deleting private notes
  • Modifying timesheets
  • SLA updated activities
  • Modifying ticket Due By time
  • Sending an email to a requester, agent, or group
  • A few things to note:

  • Even when Activities is ON, you can still click an individual note/reply/description to view the content.
  • Activities are tracked, regardless of whether they were created manually, via system automations, scenario automations, or bulk actions.
  • For better readability, concurrent activities are grouped together based on the time they occurred.
  • System activities, such as executing automation rules, will show the rule name and include a hyperlink to the Admin page. For Agents/Supervisors, only the automation type and changes will be visible.
  • Pagination in Ticket Activities

    Normal mode:

  • If there are more than 3 responses/notes, the entire conversation, except the ticket description and the last 3 responses is collapsed.
  • You can see the number of hidden responses in the collapsed block shows the number of hidden responses.
  • Activities mode:

  • If there are more than 20 activities (including replies/notes), only the first 20 are displayed.
  • Additional activities are grouped into a collapsed block with a count of hidden items. To view more than 20 activities at a time, click more.
  • For example, for a ticket with 72 activities, you may have to click three more times to see all activities.

    Labels for ticket activities

    Each activity block is labeled for quick reference. If multiple activities occur together, one label is chosen based on the priority list below:

    PriorityActivityLabel
    1Delete a ticketTicket Deleted
    2Mark as spamMarked Spam
    3Restore a ticket from trash/spamTicket Restored
    4Change ticket status<Status>
    5Assign ticket to a specific agentAgent Assigned
    6Reassign ticket to another agentAgent Reassigned
    7Change ticket agent to NoneAgent Unassigned
    8Change ticket priority<Priority>
    9Assign ticket to a specific group/Change ticket group to NoneAgent Group Changed
    10Associate ticket to a specific product/Change ticket product to NoneProduct Updated
    11Change ticket sourceTicket Source
    12Change ticket typeTicket Type
    13Add/remove tagsTag Updated
    14Execute a scenario automationScenario Executed
    15Add a watcher to a ticketWatcher Added
    16Remove a watcher from a ticketWatcher Removed
    17Change Due by timeDue Date Updated
    18SLA is updatedSLA updated