最近の検索
最近の検索はありません

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
コメント