Suite | Professional, Enterprise, or Enterprise Plus |
Support with | Explore Professional or Enterprise |
In this recipe, you'll learn how to configure clickable links within reports for tickets and knowledge base articles. When you configure clickable links, anyone viewing the report can click the link to quickly open the selected ticket or article, provided they have access.
You can create clickable links when you use the following chart visualization types:
By default, many Zendesk objects—like tickets, users, and organizations—can be opened in an Explore report by clicking on the object's ID and selecting Open link. For these objects, you don’t have to follow this recipe, but you still might choose to in order to maintain a consistent look and feel across your reports.
![]() |
![]() |
Clickable ticket link available by default | Clickable ticket link created in this recipe |
This recipe contains the following topics:
What you'll need
Skill level: Beginner
Time required: 5 minutes
- Zendesk Explore Professional or Enterprise
- Editor or Admin permissions (see Giving users access to Explore)
- Ticket data in Zendesk Support, or article data in Zendesk Guide
Configuring clickable links for tickets
- In Explore, click the reports (
) icon.
- In the Reports library, click New report.
- On the Select a dataset page, click Support > Support - Tickets, then click Start report. The report builder opens.
- In the Metrics panel, click Add and select Tickets.
-
Create a standard calculated attribute named Ticket ID converted to string with the following formula:
STRING([Ticket ID])
Tip: If you're working in a language other than English, read this article to help you enter Explore formulas in your language. - Create another standard calculated attribute named Clickable ticket ID with the following formula, replacing yoursubdomain with your actual subdomain name:
LINK("https://yoursubdomain.zendesk.com/agent/tickets/" + [Ticket ID converted to string],[Ticket ID])
- In the Rows panel, click Add and select Clickable ticket ID.
- In the Chart configuration menu (
), select Chart and set the Text interpretation field to HTML.
- Make sure the Clickable URL checkbox is selected.
Now, when you click any ticket in the Clickable ticket ID column, it will open a new browser window with the ticket.
Configuring clickable links for articles
- In Explore, click the reports (
) icon.
- In the Reports library, click New report.
- On the Select a dataset page, click Guide > Guide - Knowledge Base, then click Start report. The report builder opens.
- In the Metrics panel, click Add and select Article views.
- Create a standard calculated attribute named Clickable article link with the following formula:
-
LINK([Article URL],[Article title])
- In the Rows panel, click Add and select Clickable article link.
- In the Chart configuration menu (
), select Chart and set the Text interpretation field to HTML.
- Make sure the Clickable URL checkbox is selected.
Now, when you click any article in the Clickable article link column, it will open a new browser window with the article.
16 comments
Dainne Kiara Lucena-Laxamana
Hi 6110941897754 ,
You can configure any ID attribute into clickable links as long as there is an ID attribute for the object.
0
Efrat Barak Zadok
Can I configure clickable links to related Jira tickets?
0
Erin O'Callaghan
We've updated this article to note that clickable links are now available by default for many Zendesk attributes. As a result, we've also updated the example in this article to focus on Zendesk Guide article IDs, which aren't clickable by default but can be made clickable using this recipe.
0
Permanently deleted user
@Cheeny Aban - Thank you!
0
Cheeny Aban
Hi CaSonya,
As of the moment, this functionality is limited to what is included in this Article. We understand your need for this added functionality so I marking your comment as Product Feedback. We also suggest that you post on our Product Feedback Forum. Threads with a high level of engagement ultimately get flagged for product managers to review when they go through roadmap planning.
-1
Jon Durlauf
Any update on the ETA for clickable links for ID attributes in drillthrough?
1
Permanently deleted user
Hi, I created a query for unsolved tickets by client. Is there anyway to add the clickable link to the results? I want to be able to click on the total of unsolved tickets and see the ticket#'s associated with a link to each ticket.
0
Sabra
Hey Bharathi Kakilate! You can use the following formula in a Standard Calculated Attribute in order to create Jira hyperlinks. You'll need to replace YOURJIRASUBDOMAIN with the name of your subdomain for your Jira instance. You'll also want to make sure that the field used in the formula corresponds to the ticket field that is storing your Jira Ticket ID, which in the example is [Jira::Key].
Once you have this attribute added to your Rows panel, you'll want to double check that you've set the Text interpretation to HTML from the Chart configuration > Chart menu.
1
Bharathi Kakilate
I tried to use a similar concept of using attributes to add hyperlinks to our Jira issues and couldn't create attributes. Anyone else with this issue or found way to work with adding jira hyperlinks on explore dashboards?
(We are using Single line text to sync the Jira Ticket ID from Jira to Zendesk)
0
Henkka (Pepron)
Hi Bart,
If I understood correctly this tip earlier in the thread might do the trick:
Unrelated tip: You can easily also create user and organization links with the following calculated attributes:
And
OR
And
For your use case if I understood it correctly _ticket_ requester would be good but if you're using these for user/organization spesific queries then you could use also use Requester ID/Organization ID without _ticket_.
In the latter just keep in mind that if you've activated multiple organizations this will show you always Requesters/Users default organization while if you're doing ticket spesific queries Ticket Requester/Organization ID will always bring up the right organization based on the ticket.
Unfortunately none of these work with drillins etc for now so you probably need to do a Table query like in the example in this article
0
Sign in to leave a comment.