问题
在创建报告时,我注意到有多个不同的指标与已解决工单有关。已解决工单 和 已解决工单和有什么区别?
回答
- 在 工单数据集中找到 “已解决工单 ”指标。此指标显示帐户中当前处于已解决状态的工单数。
例如,通过将 “已解决工单” 指标与 受托人名称 属性结合使用,您可以大致了解当前处于已解决状态的工单数量,并按工单当前分配给哪些专员进行分类。但是,一旦其中一张工单切换回待回应或已开启状态,该工单将不再显示在报告中。- 如果您有 自定义工单状态 的工单属于已解决工单状态类别,这些工单也将包含在 已解决工单 指标中。
- 在 工单数据集 和 更新历史记录数据集中找到 工单已解决 指标。此指标告诉您在任何时候从不同状态更改为已解决或已关闭状态的工单数。此指标不包括从已解决状态转为已关闭状态的工单,以免重复计算工单。
在更新历史记录数据集中,此指标显示的数据取决于您的使用方式。例如,您可以将其与 工单组一起使用 属性中,查看您的每个专员组将多少工单转为已解决或已关闭状态,无论这些工单当前处于什么状态。
在工单数据集中,指标各自指定了自己的时间范围。例如, 工单已解决 - 最近 7 天。要查看工单数据集中的已解决工单指标列表,请访问此锚点链接并向上滚动:工单数据集。
一般而言,在使用时间轴(例如工单解决日期)时,您可以结合使用 工单 数据集和 已解决工单 指标。这显示了当天已解决的工单。无需切换到更新历史记录数据集,以获取关于哪些工单已转为已解决状态的日常信息。
如果您想了解某一天有多少工单处于已解决状态,可以使用待办工单数据集完成。在此了解更多关于该独特数据集的信息: 使用 Explore 分析待办工单历史记录。
翻译免责声明:本文章使用自动翻译软件翻译,以便您了解基本内容。 我们已采取合理措施提供准确翻译,但不保证翻译准确性
如对翻译准确性有任何疑问,请以文章的英语版本为准。
11 条评论
D.Fitz
I've just been notified by Zendesk Support that 1263169173630's comment above is incorrect. Ticket Solved will either return 1 or 0 for a ticket, it will NOT show each time the ticket has been solved, but will show the latest Solve only.
0
Elaine
That's good to hear! Custom reporting can indeed be challenging since I'm not able to see the whole context, and it's not uncommon to use various datasets for different aspects. If you feel the current solution is too complex, consider reaching out to the ZD support team for alternative options or optimizations. It's important to find a balance between the level of detail needed in your report and the complexity of the setup. If the current solution works for you, that's fantastic! If not, discussing it further with our support team could provide simpler insights or suggestions.
0
Elaine
I believe the reason behind that is because you are using "Updater name" attribute where it counts tickets solved by the updater (agent). I wonder if you could use "assignee name" instead to count the solved tickets via trigger to achieve your goal in this report. 🙂
0
IVAN KATALINIC
Agree with Judy's comment above. On top of the naming convention being confusing and instilling distrust, I am ending up browsing comment sections like these to find answers to my questions about how a given metric actually works - because they are not even described in well enough detail in Zendesk articles.
0
Judy Correia
Naming conventions in Zendesk Explore are not intuitive at all. Would a simpler solution to help users understand metrics be to make the name unique or more specific? Better descriptions are needed to make reporting leveraging Zendesk easier and more efficient. As an example Tickets Solved and Solved Tickets, it is not intuitive at all that these mean two different things even for native English speakers. Something like Current Status - Solved and Number of Times Solved, while maybe overly verbose provide more clarity. Confusion over the similarity in names and significant differences in results causes us to not trust Zendesk reporting.
1
WELIDG
Bonjour,
j'ai une question : comment avoir le nombre de tickets résolus dans le cas ou un ticket était résolu par un utilisateur ZD plusieurs fois, sur les rapports ZD seuls les résultats du dernier traitement sont affichés
ci-dessous un ex:
- Un client envoi une demande sur ZD le 20 mars à 8h00
- Ce ticket a été traité par un utilisateur ZD1 le 20 mars à 8h05 (statut résolu + durée traitement 5 mn)
- Le même client rebondi sur la même ticket pour poser d'autres questions, le statut du ticket passe de ''Résolu'' à ''ouvert'' le 20 mars à 8h10h
- Ce même ticket a été traité par le même utilisateur ZD1 le 20 mars à 8h11 (''Résolu'' une deuxième fois + durée traitement 1mn)
conclusion :
l'utilisateur ZD1 a reçu et traités 2 tickets avec une durée globale de traitement de 6mn ( 5mn +1mn)
mais ; sur le rapport Zendesk je trouve
- 1 seul ticket traité par l'utilisateur ZD1 + Treatment time ZD : 1mn
Comment je peux avoir le comptage des tickets résolus et la durée global sur les raports ZD? y a t il une sorte de compteur qui peut dire que tel ticket a été résolu 1,2, 3 ou plusieurs fois + la durée du traitement de chaque traitement ?
Merci d'avance
AloneInTheDark
0
Pedro Rodrigues
This is a really helpful formula, 1263082147309. I just bumped into a few cases where the formula doesn't apply because both 'previous' and 'new' values are weirdly showing up as 'solved'.
Would you know why this happens? The previous value on that update should show 'open'.
Just for reference, I managed to obtain an exact match between the Tickets dataset (Solved tickets calculated based on Solved dates) and the Updates history dataset by using the following standard calculated metric:
With this I can now accurately see resolutions above 100%, which was the expected result.
Cheers!
1
Gab Guinto
Hi Michael,
We've encountered similar cases before where the recorded timestamps of the update and for the last solved date differ by 1 or 2 seconds. You're right, this is the reason why these tickets are not being counted by the metric Tickets solved. A fix that we can recommend for this is to use a custom metric instead of the native Tickets solved metric. You can use this formula:
This formula should account for instances where there's a 1- or 2-second discrepancy between Update - Timestamp and Ticket solved - Timestamp.
0
Michael Clarke
I am currently using the Tickets Solved metric in the Ticket Updates dataset and have come across a discrepancy that I don't quite understand.

I'm using the metric to create a day-by-day query to show Tickets Created vs Solved throughout the week.
As you can see, the two Solved values don't match.
(The Solved figure under today is using the Solved Tickets metric in the Tickets dataset).
I have narrowed it down to the following scenario:
If an agent creates a new ticket and sets the status directly to solved, it is not being counted in the Tickets Solved metric.
From what I can see, the only reason why it is not being included is because there is a 1 second difference between [Update - Timestamp] and [Ticket Solved - Timestamp]
How can I fix this to ensure there are no variances?
0
Christopher Stock
Hi 364995532367, if you use the 'Tickets solved' metric within the Ticket Updates dataset you should be able to see what you need. A ticket that's been updated to 'solved' on three separate occasions would show a 3 for that metric.
0
登录再写评论。