This recipe shows you how to make ticket IDs that you include in a chart into clickable links. The report viewer can click the link, and the selected ticket will open in Support. You can quickly create clickable links when you use the following chart visualization types:
- Bullet
- Gauge
- Sparkline
With a little extra work, you can make ticket IDs in tables clickable.
In this recipe, you'll create a report that list all of your tickets with the number of agent replies. For each ticket ID displayed, you can click it to open the corresponding Support ticket.
What you'll need
Skill level: Easy
Time Required: 5 minutes
- Zendesk Explore Professional
- Editor or Admin permissions (see Adding users to Explore)
- Ticket data in Zendesk Support
How to create the report in Explore
You can click the preview below to watch a video of this recipe, or continue to the walkthrough.
- In Explore, click the query (
) icon. - In the Queries Library, click New Query.
- On the Choose a Dataset page, select the dataset containing the ticket data you'll need to build the query; in this case Support: Tickets.
Query Builder opens.
- Next, add your metrics, the things you want to measure; in this case, the number of agent replies for each ticket. In the Metrics panel, click Add.
- From the Activity section, choose Agent replies and then click Apply.
- Explore displays the results from the metric; in this case, the number of agent replies.
- Next, create a standard calculated attribute for the clickable ticket ID. In the calculations menu (
), click Standard calculated attribute. - On the Standard calculated attribute page, enter a Name for the attribute (for example Clickable link), and then enter the following Formula:
LINK("https://support.zendesk.com/agent/tickets/"+[Ticket ID],[Ticket ID])Replace support.zendesk.com with your own subdomain.
- When you are done, click Save.
- In the Rows panel, click Add.
- From the list of attributes, choose Calculated Attributes > Clickable link.
Explore displays the chart. For each ticket, the number of agent replies is shown. If you use the Bullet, Gauge, or Sparkline visualization types, you'll see that ticket links are now clickable. To get clickable links on tables, continue with these steps.
To make ticket links on tables clickable
- If you haven't done so already, from the visualizations menu (
), choose Table. - From the chart configuration menu (
), choose Chart. - From the Text interpretation drop-down list, choose HTML
- Ensure that the Clickable URL box is checked.
Now, when you click any ticket number in the Clickable link column, it will open a new Support window with the ticket details.
16 Comments
It's a pity one can't use calculated attributes in the drill through - no way to add ticket links there. Does anyone have a workaround?
I'm also looking for a way to add tickets links to the drill-through. Would love to know if there's some kind of solution
Hello Anton and Inbal,
Unfortunately this is not a feature of Drillthrough yet. This is however a great idea and I would recommend you post in the Explore Feedback Forum to make sure that our Product team is aware of this type of feature request.
When I add this clickable link attribute and add it to ROWS in a table report, it shows a ticket ID but it's not clickable. What gives?
EDIT: Disregard. For anyone with the same question, you need to add another step:
chart configuration > chart > text interpretation = HTML
You got it, Justin! Let us know if you need anything else!
Yes, would absolutely want to have clickable links in the drillthrough function as the way Insights did!
The explorer feedback link is broken. Also would like to add that clickable links is really necessary for drill through or to be able to just go into a list of the tickets and open them up the way we have in JIRA.
Here is the correct link. Please upvote.
https://support.zendesk.com/hc/en-us/community/posts/360029583513-Feature-Request-Add-calculated-attributes-to-Drill-Through-
Hi guys,
Thanks for this info allthough in our opinion this should be default behaviour - both having links to tickets, users and organizations as well as the ability to drill through on any given datapoint all the way to the ticket as this has been the X factor in Zendesk and Insights reporting. But this is what we have to live by until development!
Question - Should this Query work when placed on a dashboard? I get the link working while opening the Query directly but when placed on a dashboard it doesn't work?
Unrelated tip: You can easily also create user and organization links with the following calculated attributes:
LINK("https://YOURORGANIZATION.zendesk.com/agent/users/"+[Requester ID],[Requester name])And
LINK("https://YOURORGANIZATION.zendesk.com/agent/organizations/"+[Requester organization ID],[Requester organization name - Unsorted])I have added this calculated metric in one dataset (standard support tickets), but it's not visible when using a different dataset. So I've set it up again in the other dataset (ticket updates), but it's not showing up in rows/columns or filters. I've tried twice now.
Is it not possible within this dataset, or what is the reason to this?
I think it's absolutely ridiculous that ticket IDs aren't automatically clickable in reports, and you can't even copy the link ID, so you have to manually look up the number, having Zendesk open in a different window/tab.
So frustrating! It's adding so much extra time to ticket analysis/review/management.
This should be the default behavior for Ticket IDs like it is in Goodata.
This article is helpful, however, as others have stated, this is still a bit ridiculous that the ticket IDs and names are not automatically assigned to be clickable. Explore is such a pain in the butt to work with compared to insights that it boggles my mind that you brought it out so soon. It feels incomplete.
The interface for viewing the datasets is horribly inefficient. If you download a pdf you can't even see the entire list of information, it only shows the part that is visible within explore and you cannot even see more than a phone screen-sized portion of the report at a time. Is there a way to just easily view the information in a query?
It would also be nice if you could just change filters in a query instead of having to make numerous queries for different months or go and edit a query every time you wanted to review info. For instance, we have customer service meetings where we go over negative reviews and to look at a different month of reviews, I have to go in, update the query, then go back to the dashboard to see it, or just view it in the editing form.
I appreciate that help that has been provided via email, however, it seems like explore is currently just a large waste of time compared to how easy it was to get the same info with insights. If changes like this can be made so suddenly it concerns us as to what else might be drastically changed for no other reason to be made more costly or just become worse.
Hi Matthew Dealy, thank you for reaching out. You're raising valuable feedback:
Thanks
Hey Vincent,
Thanks for getting back to me.
• This will be wonderful! Thanks for working on that :)
• Awesome! Right now the PDFs don't export more than what you can see on screen which is really frustrating for the satisfaction query because the notes from customers become very long sometimes and it's not possible to see them entirely along with all of the other rows on the screen. The PDF export does not let you scroll sideways to see the other info. If the satisfaction comments could be made to use multiple rows in a query instead of being a super long single row, that would be ideal.
• I did figure out the last one about the month change with the data filter, thank you for that! :)
Hey Vincent,
I was able to solve the multi-line issue using the info in This article under the columns section.
The only thing to add is that it would be sweet if there were default queries that showed average first reply time and one-touch tickets with an average shown.
Thanks much!
Hey Matthew Dealy, many thanks for your replies.
Kind regards
Vincent
Please sign in to leave a comment.