Suite | Professional、Enterprise 或 Enterprise Plus |
Support 以及 | Explore Professional 或 Enterprise |
在此配方中,您将了解如何在工单和知识库文章的报告中配置可点击链接。配置可点击链接后,任何查看报告的人员都可以点击链接,快速打开所选的工单或文章,只要他们有访问权限。
使用以下图表可视化类型时,可以创建可点击链接:
默认情况下,许多 Zendesk 对象(例如工单、用户和组织)都可在 Explore 报告中打开,方法是单击对象 ID 并选择打开链接。对于这些对象,您不必遵循此配方,但您仍可以选择这样做,以便在报告中保持一致外观和风格。
![]() |
![]() |
可点击工单链接默认可用 | 在此配方中创建的可点击工单链接 |
此配方包含以下主题:
您需要什么
技能级别:初学者
所需时间:5 分钟
- Zendesk Explore Professional 或 Enterprise
- 编辑者或管理员权限(请参阅授予用户 Explore 访问权限)
- Zendesk Support 中的工单数据,或 Zendesk Guide 中的文章数据
配置工单的可点击链接
- 在 Explore 中,单击报告图标 (
)。
- 在报告库中,单击新建报告。
- 在选择数据集页面上,单击 Support > Support - 工单,然后单击开始报告。报告生成器随即打开。
- 在指标面板中,单击添加并选择工单。
-
使用以下公式创建一个标准计算属性,名为已转换为字符串的工单 ID:
STRING([Ticket ID])
提示: 如果您使用的语言不是英语,请阅读此文章,以便使用您的语言输入 Explore 公式。 - 使用以下公式创建另一个标准计算属性,名为可点击工单 ID ,以将您的域名替换为您的实际子域名:
LINK("https://yoursubdomain.zendesk.com/agent/tickets/" + [Ticket ID converted to string],[Ticket ID])
- 在行面板中,单击添加并选择可点击工单 ID。
- 在图表配置菜单 (
) 中,选择图表并将文本解释字段设置为 HTML。
- 确保已选中可点击 URL 复选框。
现在,如果您单击可点击工单 ID 列中的任意工单,将打开一个新的浏览器窗口,其中包含该工单。
配置文章的可点击链接
- 在 Explore 中,单击报告图标 (
)。
- 在报告库中,单击新建报告。
- 在选择数据集页面上,单击 Guide > Guide - 知识库,然后单击开始报告。报告生成器随即打开。
- 在指标面板中,单击添加并选择文章视图。
- 使用以下公式创建一个标准计算属性,名为可点击文章链接:
-
LINK([Article URL],[Article title])
- 在行面板中,单击添加并选择可点击文章链接。
- 在图表配置菜单 (
) 中,选择图表并将文本解释字段设置为 HTML。
- 确保已选中可点击 URL 复选框。
现在,如果您单击可点击文章链接列中的任意文章,将打开一个新的浏览器窗口,其中包含该文章。
16 条评论
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
登录再写评论。