Recent searches
No recent searches
Configurable combination of attributes in a time filter
Posted Aug 29, 2022
Requirement:
The following requirement is only one example of a limitation we run into it!
Within a monthly report we want the daily count of created and solved tickets in one diagram (report). Basically there is an example in the standard dashboards, but this has s significant limitation, which is partially also mentioned in following post:
https://support.zendesk.com/hc/en-us/community/posts/4631391640090-What-is-the-purpose-or-meaning-of-the-default-Dashboard-time-filter-reflecting-created-solved-
The dashboard is using a time filter refering to the attributes "Ticket created" and "Ticket solved". The report is excluding "Ticket solved" from the time filter. By this, for the count of solved tickets in the period given in the time filter, only tickets that are created in that time are included. Tickets solved in the set time period, but was created earlier, are not included.
If the exclusion of "Ticket solved" is removed from the time filter, then for the count of created tickets in the time period given in the time filter, only tickets that are also solved in that time are included. Tickets which are not solved in the given time frame are not included.
This means, if several attributes are used in a time filter ALL of them has to be fulfilled (combined using AND).
Feature Request:
It should be possible to configure in the time filter, if ALL (combined using AND) or ANY (combine using OR) refered attribute should be fulfilled.
Alternatives:
If there is any other alternative, to ensure that all tickets the agents are working on in the given time period can be included in a report, we would be happy. The attribute "Ticket updated" in the time filter is not working for use, because it includes updates done by triggers, automations and internal procedures of Zendesk (e.g. closing a ticket).
7
4 comments
Orville Herndon
2nd this request as we've also hit this limitation with time filtering.
1
Reed David
We just ran into this limitation too. This seems like a basic requirement for time filters, I'm really surprised this isn't possible.
0
Eugene Orman
Thank you for sharing your feedback. I see what you are trying to achieve. Have you tried using the Updates dataset for this purpose? You could look at all tickets that were updated at least once during a specific time range:

0
Torsten Serfling
Hello Eugene Orman
The dataset "Updates History" has the same limitations.
Using "Update - Date" does not meet the requirements, because it returns all tickets updated in the given time frame. That doesn't mean, that them are created or solved in the given time frame. Furthermore this also includes system updates (e.g. ticket status changed from solved to closed).
Torsten
0