Data discrepancies between Ticket created date and Ticket solved date | Community
Skip to main content

Data discrepancies between Ticket created date and Ticket solved date

  • December 6, 2022
  • 4 replies
  • 0 views
Levon

Hi all,

We managed to export the data from Zendesk to our data warehouse to build some reports in our Business Intelligence tool, and we are facing couple of data discrepancies we would like to understand.

In Explore, we would like to get the number of tickets solved by agent on a monthly basis (assignee).

When we apply [Ticket Created] date as a dimension in the rows, we get different numbers than when we apply [Ticket Solved] date as a dimension. 

Could you clarify us if it's normal and if yes what's the best way to measure this metric?

    4 replies

    Jahn11
    • Jahn11
    • December 6, 2022

    If you want to get the monthly "SOLVED" tickets by each agent you will need to use the filter Ticket Solved Date.

    If you will use Ticket Created Date filter to measure the solved tickets by each agent, you will only get the number of solved tickets based on the ticket create month. 

    Levon
    • Levon
    • Author
    • December 6, 2022

    Thanks Jahn for you reply, that what I was thinking honestly. 

    Since we are working with the data through our data warehouse in SQL, logically we would need to take the date of the solved_at column right (and not created_at) ?

    Jahn11
    • Jahn11
    • December 6, 2022

    Yes, if your goal is to get the number of Solved Tickets per agent per month. In this case you will also be able to get those solved tickets that are not created only from this month for example. 

    CJ99
    • CJ99
    • December 6, 2022

    One thing that may bite you as well -- you should also be aware that "Solved Tickets" on the Updates History dataset is a known bad metric that returns bad data. There's a workaround formula you can write to make it correct: https://support.zendesk.com/hc/en-us/community/posts/4811432683034-Tickets-solved-metric-discrepancy-in-Updates-history-Explore-dataset



    Terms & ConditionsCookie settingsAccessibility statement