Explore recipe: Reporting on created and solved tickets

Have more questions? Submit a request

12 Comments

  • Bill Cicchetti
    Comment actions Permalink

    Hmmm when I expand the Tickets choice list under Metrics I don't see a Tickets Created option
     

    0
  • Stephen Fusco
    Comment actions Permalink

    Hello Bill, 

    Thank you for reaching out to us. Based on your screenshot it looks like you've selected the wrong dataset. You'd want to select the dataset called "Support: Ticket Events" from the looks of your screenshot it appears you've selected the "Support: Tickets, Users, Organizations" dataset instead. 

    Because we are tracking ticket events we'd want to use that dataset. Event metrics are not available in the other datasets. I hope that helps! 

    0
  • Bill Cicchetti
    Comment actions Permalink

    Thanks Stephen!

    0
  • Ann Verstraete
    Comment actions Permalink

    The amount of tickets solved on a day differs from the information I gather out of the dataset "Support: Tickets, Users, Organizations". In this last dataset the solved tickets are calculated based on "date tickets solved" whereas in this example it is calculated based on "update date". Any idea what is creating the difference in these values?

    1
  • Molly
    Comment actions Permalink

    Hi Ann,

    Thanks for reaching out! I'm going to send you a ticket so I can follow up and get some more specifics on your reports. Stay tuned for that update.

    0
  • Traian Vila
    Comment actions Permalink

    Hello,

    Whenever we use "Ticket created by Month" and date range from Aug 2018 until Today we get January and February 2019 starting on the X axis and following the 2018 months. Is there any way to rearrange them, eg. put Ian/Feb 2019 at the end of interval ?

    Thanks,

    Traian

    0
  • Bill Cicchetti
    Comment actions Permalink

    Hi Traian,

     

    Have you tried adding Ticket-Created Year for the x-axis and placing that before the Ticket- Created Month in the list of columns?

    When I flip those back and forth with these two the placement changes the ordering of the months on the axis

    0
  • Traian Vila
    Comment actions Permalink

    That works ! Thanks a lot Bill !

    0
  • Sarah Anscombe
    Comment actions Permalink

    Is there any way to report on solved tickets only? On the dashboard, the pop up message states solved and closed tickets.

    Thanks

     

    0
  • Delores Cooper
    Comment actions Permalink

    Hey Sarah! 

    Solved tickets transition to closed tickets via automation 4 days after they have been set to solved (this is a default automation so this statement only applies if you haven't adjusted this automation in your Zendesk instance). This is why the dashboard shows both solved and closed tickets in that data point.

    Can you explain your use case a bit more and what you're ultimately trying to see? With more information I may be able to recommend a workaround. :)

     

    Thanks!

    0
  • Sarah Anscombe
    Comment actions Permalink

    Hi Delores - thank you for coming back to me.
    I wanted to know if a ticket will appear in the query/ dashboard if set to solved and then show again in four days when changed to closed?

    This would mean that the reporting is not accurate for tickets we are actually solving if they appear twice.

    Thanks

    Sarah

    0
  • James Sanford
    Comment actions Permalink

    Hey Sarah!

    I wanted to know if a ticket will appear in the query/ dashboard if set to solved and then show again in four days when changed to closed?

    The ticket will only be counted once when using the default standard calculated metric for Solved tickets.

    0

Please sign in to leave a comment.

Powered by Zendesk