When I clone the default Support dashboard, and look at the properties of the time filter, it indicates that it is applied against the ticket solved AND ticket created fields. Is this a statement that it's all tickets solved OR created within the range, or tickets solved AND created?
In the OR case, this seems to make sense, but in testing it looks like the filter is being expressed as the AND case. If that is correct, that data reflected in the widgets/queries is only for tickets both created AND solved within the range, is there a specific value or meaning or story to this logic window? (ie Solve date could be described as 'What we worked on' and create date could be described as 'What we're working on'.)
From here, why are different data points excluded in the default simple queries? Like, I apply the AND filter above, but the for the Tickets Created, it excludes solve date, which is a component of the date filter; the same with the unsolved tickets, but it's excluding solve date. Is this some kind of compensation for using the AND version of the filter?
Is this compensation is part of the Explore recipe design pattern, and should I be building these filter exceptions into every query or checking whether I need to strip them whenever I create them?
I revised my date filter to filter on date updated, and to pull in data for tickets updated in the date range. It's noisier reporting, but it foots. Is there a way of stripping out the 'exclude filters' settings of multiple widgets in bulk?
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.