最近搜索
没有最近搜索

DJ Yoder
已加入2021年4月15日
·
最后活动2022年7月18日
VP, Customer Support Upland Software, Inc. uplandsoftware.com
关注
0
关注者
0
活动总数
34
投票
10
订阅
17
活动概览
标记
文章
帖子
社区评论
文章评论
活动概览
的最新活动 DJ Yoder
DJ Yoder 进行了评论,
This functionality works fine for us. However, it doesn't seem that views or reports have any parameters to pull problem tickets that have linked incidents or incidents that are linked to a problem. Or any ability to report on how many linked incidents any given problem has. The only visibility into the association is at the individual ticket level. That added layer of insight is really important for us. Any plans on this for the future or other ways to solve for this other than custom API reports?
查看评论 · 已于 2022年7月18日 发布 · DJ Yoder
0
关注者
2
投票
0
评论
DJ Yoder 进行了评论,
Agree, this is a major deficiency for us in incident management. We've had to create custom fields and manage them manually to keep teams in the loop. Also for historical reporting, there is no way to report on the count of incidents related to a problem. or to know if a problem ticket ever even had multiple incident tickets in the first place.
查看评论 · 已于 2022年7月18日 发布 · DJ Yoder
0
关注者
4
投票
0
评论
DJ Yoder 进行了评论,
When you solve the problem ticket and then choose the option to also solve all associated incidents, it ignores fields on the related incidents that are not yet filled out but are required on solve. We are ending up with tickets with incomplete field data as a result. Is this intended (there is no warning that it will override "required field" settings)? Or is this a bug?
查看评论 · 已于 2021年11月10日 发布 · DJ Yoder
0
关注者
3
投票
0
评论
DJ Yoder 进行了评论,
Agree with everyone here, I'm trying to come up with a simple report of a list of problem tickets with a metric column of number of incidents raised against that problem. Seems like that should be pretty standard report in terms of incident management.
查看评论 · 已于 2021年10月07日 发布 · DJ Yoder
0
关注者
8
投票
0
评论
DJ Yoder 进行了评论,
Yes! You severely limit new feature adoption when you don't consider the level of effort for existing users to implement that feature. In this case, having to manually update 1000+ triggers isn't feasible. We can bulk deactivate, why can't we bulk "update category"? Seems like a fairly straight-forward addition to the development cycle before rolling the feature out.
查看评论 · 已于 2021年6月02日 发布 · DJ Yoder
0
关注者
2
投票
0
评论
DJ Yoder 进行了评论,
Hi! Have you ever looked into the problem/incident functionality? Not sure if it fits your use case exactly without having more details, but my team uses this to post one update that notifies all related incident tickets at once. No ticket merging and no individual updates or BCC notifications are required. https://support.zendesk.com/hc/en-us/articles/203691086-Working-with-problem-and-incident-tickets
查看评论 · 已于 2021年2月17日 发布 · DJ Yoder
0
关注者
0
投票
0
评论