Insights recipe: Reporting on created and solved tickets

Return to top
Have more questions? Submit a request


  • Rich Lorenzo

    I have another question now: I'm trying to create a metric that will show % of tickets more than 2 days old.

    This would be very easy with actual SQL but I'm at a complete loss how to build this metric in GoodData. Basically, I don't know how to determine the number of tickets meeting the criteria:

    - Not Closed, Solved, Deleted

    - More than 48 hours since the ticket was created

    Is there any concept of the current time available in GoodData?

    I found this "Fact" Ticket Created at (Minutes) but I'm not really sure what that means. And I would still need to know the current time to do any sort of calculation and logical decision based on the amount of time between created and "now".

    I have a feeling this is not going to be possible to do the way I am trying to do it. Does anybody have any ideas?

  • Graeme Carmichael
    Community Moderator


    Creating hourly measures in GoodData is a little dangerous as the feed from Zendesk is not real time. For that kind of monitoring of unsolved tickets, it may be better to use a view. Views are real time and are a good way of managing live tickets.

    In GoodData, the macro THIS points to the current date, but not the current time. So the easy way to monitor unsolved tickets 2 days and older is:

    Just for fun, to attempt an hourly report in GoodData, you can try:

    The base date for THIS and the ticket created at minutes are not the same, so some manipulation is needed. There is also daylight saving to consider too. I would not recommend this route.

  • Rich Lorenzo

    Thanks Graeme, this is very helpful. I'm very much aware that the data feed is not real time. My thinking was that I would be able to rationalize "Ok, so that's the % of tickets older than 48 hours as of 3 hours ago". 

    However, it seems there are other things I hadn't considered. I think your suggestions can help me get close enough to what I was trying for. Basically, average age of open tickets is not a helpful metric when one ticket could be lingering, for very good reason, for months and skew the average. Perhaps I could try something more like median ticket age but I still would prefer something that shows me % of open tickets above a certain age.

    I'm sure there are plenty of other ways to paint the picture I'm trying to paint in my dashboards, I just wish it didn't require so much arcane knowledge and creativity. Thanks for your help, without these forums building these reports for my exec dash would be truly a nightmare..

  • Lisa Nanoff


    I'm creating a report on the average first reply time by calendar week.

    I've set the What ? to "AVG first reply time in hours". When setting the How? I noticed a considerable difference in time between "Week (Mon-Sun)(Ticket created)" and "Week (Mon-Sun)(Ticket solved)".

    What is the difference between these two metrics and why to they give such different results? When looking at the Reporting overview, it seems the built in avg first reply time corresponds to "ticket solved", why would this be more appropriate that "ticket created"?



  • Jacob J Christensen
    Community Moderator

    Hi Lisa,

    The filters by week determine what tickets you're reporting on.

    Are you looking to report on tickets that were created in that week or tickets that were solved that week? There is probably some overlap, but it will not be exactly the same tickets, so the time could vary significantly.

    Does that make sense?

  • Lisa Nanoff

    Thanks Jacob!


    That clears things up! 

  • Imran Rabbane Sawjet



    I can't add Date(event) in How panel. Can you please share what is the problem?

  • Brett Bowser
    Zendesk Community Team

    Hi Imran,

    What metric are you using under the What tab? It's possible the Date(event) attribute is not compatible with the metric you're using.

    Let me know!

  • Erin Shevlin

    I'm trying to run a report that shows how many tickets were solved by our "bump bump solve" trigger when a customer doesn't respond to a pending ticket. Any suggestions on how to accomplish this?

  • Pedro Rodrigues
    Community Moderator

    Hi Erin Shevlin, you can create a trigger that detects that the status changed from pending + status changed to solved + contains tag (or whatever you use to make sure the ticket is in the bump bump solve workflow). Then you add a specific tag to that ticket, which you could use in reporting.

    Alternatively and providing a more detailed solution, I usually do that by adding an additional tag that is never deleted from the ticket.

    • Let's say that the business rule that updates your ticket adds the tag inactive_enduser_solve
    • You would then also add the tag metrics_inactive_enduser_solve to that rule, for example

    Assuming you have a trigger that removes the first tag if the customer replies (in order to reset the workflow), that same trigger shouldn not delete the second tag (the one that contains "metrics_"), which will always be added to the ticket.

    This way you'll be able to see how many tickets are:

    • Solved without inactivity (does not contain neither inactive_enduser_solve nor metrics_inactive_enduser_solve)
    • Solved with inactivity (contains inactive_enduser_solve)
    • Solved, where inactivity was applied but later reset (does not contain inactive_enduser_solve + contains metrics_inactive_enduser_solve)

    Hope this helps!


Please sign in to leave a comment.

Powered by Zendesk