Explore recipe: Reporting on created and solved tickets

Return to top


  • Casey Moore

    This article is really helpful, thank you!

    Does anyone know how I can find the following:

    1. Tickets created yesterday (this one I have)
    2. Of those tickets, how many were solved?
    3. Of those solved tickets, how many were one-touch?

    This is what I have so far but it's not quite there yet.  This shows me how many tickets were created (yesterday) compared to how many were solved yesterday.  Right?  

    So... if I have 100 tickets created yesterday, how many of those 100 tickets were solved yesterday?  Let's pretend it's 50; of those 50 tickets (which were created and solved on the same day) how many were one-touch?

    Help me Obi Wan...  You're my only hope.


  • RJ Hines

    Hey Casey,

    I had the exact same scenario and need a few months back. The last bit you're after - the COUNT(One-touch tickets) metric - does not exist in the Ticket Updates dataset.

    If you're looking to get all three pieces of data you identified into a single visual, you'll need to use the Support: Tickets dataset.  In my example below, I added my three metrics then used filters for Ticket Created + Ticket Updated attributes, both set to 'Yesterday':

    The only real downside to this visual is we can only view one day at a time due to how the dataset's date/time filters work, but this is all we need.

    Hope this helps!

  • Adam Hanna

    Does anyone have a way to do similar to what @... did above, but for a week long view instead of just daily. Looking to have tickets created by day of the week and of those tickets, how many were solved that same day - doesn't need to include one-touch tickets

  • RJ Hines


    Without that third metric involved, you would want to use the Ticket Updates dataset instead. I added the default system metrics Tickets Created and Tickets Solved, then set the date range. In the example below, I used 'Last Week' as my timeframe, and for flavor also added a Ticket Created - Date filter to remove Saturday/Sunday's values.

    Hope this helps!

  • Mark Leci

    RJ Hines I might be wrong, but I think your graph above is the same problem I'm running into, which is that instead of 'tickets created or solved on x date' you have 'tickets created on x date that were also solved'. This has been a problem for me because what I want is 'all the tickets that were created or solved on x date', i.e. the delta. If I try to do that using the ticket created date it's wrong as noted, if I use the 'date updated' the graph shows maybe 5x as many tickets for last week as it should. I haven't yet been able to figure this out. 

  • Monica Maldonado

    Hi Mark Leci 

    Did you get your answer?

    I am running this query and i get 40k created tickets and 50k solved ones in one day, so I am assuming (maybe wrongly) that the solved ones are not only those created in that day. Am i wrong?

    I am actually looking for the data that answer me how many unsolved Tickets i got in a specific day, and these calculations are the ones i need. So if i know how many tickets were created from the beggining until that specific date and how many tickets were solved from the beggining unitl that date i ll get the outstanding number of tickets on that specific date. 

    So far, i have been unable to get that right number.

    Let me know if you got any answer on your question please.


  • Marco
    Zendesk Customer Care
    Hi Monica! Thanks for the comment. 
    I see what you mean. Basically, this would be caused by the having to choose what time filter to use (either ticket created - date or ticket solved - date). This is resolved by creating two different queries, created tickets uses the ticket created - date time filter, and the solved tickets using the ticket solved - date filter. This is how it is done in the pre-built dashboard for Support. Then it would be a matter of putting both those queries on the same dashboard. 
    Hope this clarifies it for you! Cheers!  
  • Monica Maldonado

    Thanks for the answer Marco.

    To be honest i am still not convinced. so i can see the created tickets at any point, but when talking about solved tickets in a past date, this number is not stable as it changes due to reopened tickets right? so if i want to see how many tickets outstanding i had on the 31/12/2021 i am not gonna get the same number I had if i was checking on the 31st dec. 

    I am only finding numbers for live outstanding but nothing historical. Am I wrong?

  • Bill Cicchetti

    H Monica,

    I have had trouble with this report in the past. Support has told me to use Update-Month and Update-Year for your date restrictions.

    I did data validation and the numbers match if I run the reports date just for Total ticket Assigned (using date assigned) and Ticket Solved (using date solved). I also used in my metrics D_Count instead of Count.  

    Hope that helps

  • Monica Maldonado

    Thanks Bill Cicchetti for the time and effort. 


  • sarah aasland

    Does anyone know if it's possible to pull up a list of the individual tickets that are being counted when you click on the KPI metric?

  • AMU Cx Lead

    This query is close to what I need, but I can't figure out how to make it work for my purposes. I have an agent that works outside of our business hours on the weekends (Saturday & Sunday), and I need a query to show the following:

     - All tickets created between end  of business on Friday, to the end of Sunday.

    - What percentage of those tickets they updated to "pending" on Saturday and Sunday.

    - What percentage of the total available tickets they solved each day.

    Simply calculating how many tickets they solved isn't enough data given what we do, and only counting tickets received on the day that they work also isn't enough because of the surge of tickets we receive on Friday night.  I need to determine how many tickets they are neglecting to touch during their two-day shift so as to establish possible knowledge gaps.

  • Dane
    Zendesk Engineering
    Hi Sarah,
    You can use the Drill-in function to show the individual tickets. More information can be found in Using drill in to refine your queries.
    Hi AMU Cx Lead,

    All tickets created between end  of business on Friday, to the end of Sunday.


    For this one, you can use the standard calculated metric below. In addition, don't forget to adjust the metric filter so that it will only show tickets with the "1" value.

    IF (IN([Ticket created - Day of week],ARRAY("Saturday","Sunday"))
    AND IN([Ticket created - Hour],ARRAY("0","1","2","3","4","5", "6","7","8","9","10","11","12", "13","15","16","17","18","19", "20","21","22","23")))
    OR (IN([Ticket created - Day of week],ARRAY("Friday"))
    AND IN([Ticket created - Hour],ARRAY("17", "18","19","20","21", "22", "23")))
    THEN [Ticket ID]


    What percentage of those tickets they updated to "pending" on Saturday and Sunday.

    The query below shows how many tickets were set to Pending using the Metric above.


    What percentage of the total available tickets they solved each day.


    You can use the result metric calculation below.


    Don't forget to adjust the display format to "%".
    A final reminder: Please take note that we don't support building queries, dashboard and formulas from scratch. The information should give you an overview and serve as a guide on how to create one.
  • AMU Cx Lead

    Dane Thank you for the reply, however, when I perform the tasks you outline and add the Ticket Status attribute, it removes "new" tickets for the results?

  • Paul Jarman

    The original poster here seemed to include an image , which I'm unable to view on the post still...

    Having read through the thread, I'm still confused about how I can have the following 2 KPIs (can be simple numbers rather than graphs).  It's a simple dashboard and so I'm trying to achieve the following...

    1. Tickets created  (easy and in place using standard metric)

    2. Of those tickets in KPI 1, which are currently SOLVED or CLOSED.

    Everything I try seems to give me total crated / solved on any given time period, rather than KPI 2 being a subset of KPI 1.

    Hope that's clear and that someone can help :-)


  • Dane
    Zendesk Engineering
    Hi Paul,
    Can you check Explore recipe: Reporting on created and solved tickets if it will work for your use case? 

Please sign in to leave a comment.

Powered by Zendesk