What is the difference between the solved tickets and tickets solved metrics?

Return to top
Have more questions? Submit a request


  • Violeta Micu
    Community Moderator

    Hi Elissa


    How can you add Assignee together with the Tickets Solved metric if the Assignee is not existing as an attribute in the Ticket Update dataset?


  • Elissa
    Zendesk Community Team

    Hello Violeta Micu

    Very good point! I'm so sorry for the mistake! I've updated the article now to show a realistic example where "ticket group" is used, which is actually an attribute in the ticket updates dataset!

    Sorry again for the mistake and thanks so much for helping me get that corrected!

  • Violeta Micu
    Community Moderator

    Thank you Elissa


    Now can you confirm that  "But, as soon as one of those tickets switches to Closed it will no longer show in the report." in The Tickets Dataset? I am seeing different behaviour. Closed tickets are also shown in Tickets Dataset when you use Solved Tickets Metric.


    Thank you,

  • Elissa
    Zendesk Community Team

    Hello Violeta Micu

    Thank you again. Wow I'm very sorry about this! You are correct that I explained that poorly. The Solved Tickets metric includes both "solved" and "closed" tickets. So really a better way to explain the functionality would be to say "But, as soon as one of those tickets switches back to Pending or Open, it will no longer show in the report".

    I've updated that as well and am going to review this whole article once again to try and make sure there are no other oversights. Please do let me know if you find anything else that is inaccurate or out of place. 


  • Rodger Bradford

    Hello Elissa, 

    I am trying to find the best way to quantify the amount of work done by an agent during a given date range.  I had always relied on the COUNT(Solved Tickets) metric but after reading your article, I am not so sure.  Hopefully, you can help me better understand the data that we are reporting.

    According to the definition of Solved Tickets being the number of solved tickets assigned to an account (group or agent), wouldn't many of the tickets show in the report for each day they remain in solved status until they are closed?  

    For example, ticket# 1234 is solved on Monday and it shows in the report for Solved Tickets for that date.  On Tuesday, that same ticket remains in Solved status.  Would it show in the reporting data for Tuesday, even though it was moved to Solved status on Monday?

    If this is the case, it appears that using Tickets Solved would be a better metric to show the amount of work being done by a group or agent for a given date.  Is this correct?

    Thank you. 



  • Elissa
    Zendesk Community Team

    Hello Rodger Bradford,

    I'm glad this article was able to shed a bit of light and help you reorganize your report. It does sound like you are on the right track!

    What I like to do when creating new reports, is to take some time look at what tickets are making up each column in my report. This helps me double check and validate that the data is showing what I think it should be. The way I like to do this is to use the decompose feature, with the Ticket ID metric. For example, if I have a column chart, showing #tickets solved by date, I will click on the column that shows 5 tickets for a certain date, and select decompose and select Ticket ID. Like this:

    So the decompose feature shows you the ticket IDs that make up that set of data, and you can check to see if those tickets were in fact moved to a solved status on that date.

    Just another quick note on your particular report setup:

    Time is kinda tricky/different. Generally when using a time X axis, you can use the Tickets dataset (with solved tickets) and you will see the tickets that were solved on the given day. So no need to switch over to the Ticket Updates dataset to try and get day by day information on what tickets were moved to a solved status.

    This is where a third one of our datasets comes into the mix: the Backlog dataset. If you do in fact want to see a snapshot of how many tickets were in a solved status on any given day, you can use the Backlog dataset to do that. Learn more about that unique dataset here: Analyzing your ticket backlog history with Explore.

    I hope that helps!

  • Rayann Quirk

    Hello Elissa, 

    Similar to Rodger's question, I am trying to find the best way to quantify the amount of work done by an agent during a given date range.  I am using the tickets solved metric but in reading your article, I'm not sure it will give me the true number of ticket solved events.

    For example, if a ticket is solved multiple times by multiple assignees, would the solved ticket metric only use the most current solved date? If a ticket is solved on Monday by Assignee A, reopened and solved again on Tuesday by Assignee B, reopened and solved again on Friday by Assignee C, would the solved ticket event only show on Friday by Assignee C? If I pull a report on Saturday, Is there a way to get all solved Ticket events for single/unique Ticket? Thanks!

    • Ticket 123 - Solved Monday - Assignee A
    • Ticket 123 - Solved Tuesday - Assignee B
    • Ticket 123 - Solved Friday - Assignee C
    • If I pull on Saturday, Total Ticket Solve events for Ticket 123 should = 3
  • Chris Stock
    Community Moderator

    Hi Rayann Quirk, if you use the 'Tickets solved' metric within the Ticket Updates dataset you should be able to see what you need. A ticket that's been updated to 'solved' on three separate occasions would show a 3 for that metric.

  • Michael Clarke

    I am currently using the Tickets Solved metric in the Ticket Updates dataset and have come across a discrepancy that I don't quite understand.
    I'm using the metric to create a day-by-day query to show Tickets Created vs Solved throughout the week.

    As you can see, the two Solved values don't match.
    (The Solved figure under today is using the Solved Tickets metric in the Tickets dataset).

    I have narrowed it down to the following scenario:
    If an agent creates a new ticket and sets the status directly to solved, it is not being counted in the Tickets Solved metric.
    From what I can see, the only reason why it is not being included is because there is a 1 second difference between [Update - Timestamp] and [Ticket Solved - Timestamp]

    How can I fix this to ensure there are no variances?

  • Gab
    Zendesk Customer Advocate

    Hi Michael,

    We've encountered similar cases before where the recorded timestamps of the update and for the last solved date differ by 1 or 2 seconds. You're right, this is the reason why these tickets are not being counted by the metric Tickets solved. A fix that we can recommend for this is to use a custom metric instead of the native Tickets solved metric. You can use this formula:

    IF ([Changes - Field name]="status" AND [Changes - Previous value]!="solved"
    AND ([Changes - New value]="solved" OR [Changes - New value]="closed")
    AND ([Ticket status - Unsorted] = "Solved" OR [Ticket status - Unsorted] = "Closed")
    AND ([Update - Timestamp]=[Ticket solved - Timestamp]
    OR DATE_TO_TIMESTAMP([Update - Timestamp])=DATE_TO_TIMESTAMP([Ticket solved - Timestamp])+1
    OR DATE_TO_TIMESTAMP([Update - Timestamp])+1=DATE_TO_TIMESTAMP([Ticket solved - Timestamp])
    OR DATE_TO_TIMESTAMP([Update - Timestamp])=DATE_TO_TIMESTAMP([Ticket solved - Timestamp])+2
    OR DATE_TO_TIMESTAMP([Update - Timestamp])+2=DATE_TO_TIMESTAMP([Ticket solved - Timestamp])))
    THEN [Update ID]

    This formula should account for instances where there's a 1- or 2-second discrepancy between Update - Timestamp and Ticket solved - Timestamp.


Please sign in to leave a comment.

Powered by Zendesk