- You want to display results only between certain dates
- You want to restrict results to a certain group
- You want to make a large report more manageable by restricting the results
- Filter by metrics: All of the metrics added to the Metrics panel are affected by the filter you add. For example, you can filter the Tickets metric to show only tickets that were created last week.
- Filter by individual attributes: Only the attributes you've set a filter for are affected by the filter you add. For example, you can include only the names of your team members in a report result.
This article contains the following sections:
Example: Filtering by metrics
In this example, you'll add a count of all tickets and a count of all solved tickets to a report. You'll then filter the results to show only tickets created last week.
To create and filter the report
- Open a new, blank report using the Support: Tickets dataset. For help, see Creating reports.
- In the Metrics panel, click Add.
- From the list of metrics, choose the following two metrics:
- Tickets > Tickets
- Tickets > Solved tickets
- When you are finished, click Apply. Explore displays the total number of
tickets and the total number of solved tickets in your Support
instance.
- Next, add a filter to restrict the results to only show tickets created last week. In the Filters panel, click Add.
- From the list of filters, you can choose any attribute to add as a filter. For example, you could choose Ticket > Ticket channel to restrict the results to only a specific ticket channel or Assignee > Assignee name to show only tickets assigned to specific people. In this case, you want to show only tickets created last week. From the list of filters, choose Time - Ticket created > Ticket created - Date.
- When you are finished, click Apply. You'll notice that the report results haven't changed. This is because you need to configure the filter to display only the values you want.
- In the Filters panel, click the Ticket created - Date filter you just added.
- The filter panel opens. By default, you'll see a list of all possible values
listed. You can check or uncheck the values you want to include in the report
results.Tip: Only the first 100 values are shown in the list. To show more values, click the arrow next to the Apply button.
In this case however, you want to select a date range, in this case "last week". Click Edit date ranges.
- On the Date range panel, you can configure simple date ranges like
Today and Yesterday and more advanced date ranges like 20
days in the past. For this example, choose Last week, then click
Apply.
The report results update to show only tickets and solved tickets created last week.
You could now add attributes to slice these filtered metrics by anything you want like assignee name, ticket status, and more.
Example: Filtering by attributes
In this example, you'll create a report that displays the assignee name and ticket status for all tickets in your Support instance. You'll then filter this to show only tickets assigned to you.
To create the report
- Open a new, blank report using the Support: Tickets dataset. For help, see Creating reports.
- In the Metrics panel, click Add.
- From the list of metrics, choose Tickets > Tickets, then click Apply. Explore displays the number of tickets in your Support instance.
- In the Rows panel, click Add.
- From the list of attributes, choose the following two attributes:
- Assignee > Assignee name
- Tickets > Ticket status
- When you are finished, click Apply. Explore displays a table showing each
assignee name and the number of tickets they have in each ticket
status.
- Next, you'll filter on the Assignee name attribute to include only yourself in the results. In the Rows panel, click the Assignee name attribute.
- On the Assignee name panel, select the checkbox next to your name. If the
list of names is long, you can type the first few characters to narrow down the
list. You can add multiple names if you want. When you are finished, click
Apply.
Explore displays only tickets assigned to you and the number of tickets in each status.
Other filter types
Another type of filter, the metric filter enables you to set a minimum or maximum value for your results. For more information, see Selecting the metric result range.
You can also apply filters to your dashboards. When you do this, dashboard viewers can directly control the filters to modify the report. For more information, see the following two articles:
18 Comments
Hi I'm currently trying to separate tickets by its previous updates.
For example, I want to identify ticket IDs that have been updated to have a "High" priority at least once in its lifetime.
But other than that I also want to know every single update for each ticket IDs that meets that criteria.
Filtering with "Update Ticket Priority" or "Changes - New Value" to "High" would only show the updates that have "High" priority meanwhile as I said before, I also want to show all of the updates of the said ticket IDs.
Any tips on how I could perform such filter/selection?
Hi Alfine,
If I'm following your question correctly, I do have some ideas that can help!
For starters, you can create a standard calculated metric which will pull updates where the priority was set to high, like in the screenshot below. For more on building standard calculated metrics you can check out this article from our knowledge base: Creating standard calculated metrics and attributes
Next, you can create a second standard calculated metric like so:
This metric will show a 1 for every update that occurred on a ticket that had the priority set to high at any point in time. This will be more clear below. When we add both of these metrics to a query, along with the Ticket ID and Update - Timestamp as Rows of the query, we can start to see how this works.
The last step is to filter out the unwanted tickets, which you can do with a metric filter on our Attribute Fix metric. More on metric filters can be found in this article in our knowledge base: Selecting the metric result range.
Now, we have a base query as you describe, which allows us to see every update event, specifically on tickets that were ever set to a high priority:
Then, you can pull in any other data elements you want added to the query.
Hopefully this helps as a starting point for the query you have in mind!
Hi @...!
Thank you so much, I have tried it and it worked like a wonder.
Although I still don't know about the ATTRIBUTE_FIX() function on the query. Do you have any documentation I can read to get to know how this function actually works? Would be much appreciated.
Thank you.
Hi Alfine Putra Dhanendra, the aggregation level functions like ATTRIBUTE_FIX have not been officially released yet, but you can read more about them at:
https://support.zendesk.com/hc/en-us/community/posts/360044181213
Thanks!
@...
We're currently trying the Professional level of Zendesk, and one of the biggest tasks we want to undertake is exporting our tags which we use to track our stats. Currently we're seeing a lot of metrics for sorting by numerical fields. But is there a way to do keyword searching/sorting, and filter those by date as well?
Thank you in advance!
Hi Matt Halvorson, I don't know of an easy way to do these because Explore doesn't track WHEN a tag was added. However, I'd recommend you ask this over in our Explore Q&A section as it's possible that folk over there might have a solution. Thanks!
Thank you for the feedback! I'll reach out on that thread.
Hello,
What is the limit of tags I can filter with? In Insights, the limit was 200. When trying to add more tags to the current filter, I receive a "Narrow down your query" message. Does this mean I have maxed out the amount of tags I can filter against?
Thank you in advance!
Hi Christine,
The error 'Narrow down your query' means the there is too much data from the query results. Technically, you can select as much tags as you need in your tag attribute filter, but if the resulting data is too huge for Explore to process, you may still be hit with the network error or the narrow down prompt. You may need to add more filters to the query (e.g., narrow down the report by a date attribute) in order to successfully load the query.
By the way, in case you haven't reviewed this doc yet, here's a guide on Reporting with tags in Explore.
Hi Gab,
Thank you so much for the info! We can't narrow the query down more since we are reporting on the last 7 days but knowing that there is no tag limit does definitely help. Thanks for including the link to reporting with tags, I appreciate it!
Can I please get instruction on how to change these metrics?
Darron Shubin It sounds like you want to create custom Full Resolution Time brackets. If so, you can duplicate the standard Full Resolution Time Brackets attribute and update the formulate to reflect the specific timeframes you'd like to bucket the resolution results in. Hope that helps!

Hello,
These articles here are really helpful! Thank you!
I was wondering if there is a way to make filters conditional.
I am applying two data filters on my Guide reports: One to filter between our internal and external Knowledge Base and the second to filter between the categories of our external KB.
My question is: is there a way to show the second filter only if the 'external KB' is chosen in the first filter? That would be really cool!
I hope all is well! I am glad you are enjoying the Explore material! Unfortunately, it is not possible to work with a conditional configuration for filters yet. We have acknowledged your feedback!
Thanks!!
Hi,
I've created a report using attribute with some conditions but just some of conditions are met for a specific time. I choose that specific time range but nothing changes. Should I change anything else in time range?
Attribute filters always look at the current value of fields or ticket properties, so filtering by a specific time frame wouldn't pull the previous values selected at that time. If you need to look at historical data, then you can try exploring the reporting options under the Updates history dataset, specifically the Ticket field changes attributes. You can check out this post by Erik and see if you can implement a similar workaround that may work for your report.
Thanks Amin!
Thanks @... for response,
In my case, some of conditions are met, and some not. I just wonder why there is this difference.
Let me create a ticket so that we can take a look at the report saved in your account. You'll receive an email from us shortly. Thanks!
Please sign in to leave a comment.