Ricerche recenti
Nessuna ricerca recente

DJ Yoder
Data ingresso 15 apr 2021
·
Ultima attività 18 lug 2022
VP, Customer Support Upland Software, Inc. uplandsoftware.com
Seguiti
0
Follower
0
Attività totali
34
Voti
10
Abbonamenti
17
PANORAMICA ATTIVITÀ
BADGE
ARTICOLI
POST
COMMENTI NELLA COMMUNITY
COMMENTI AGLI ARTICOLI
PANORAMICA ATTIVITÀ
Ultima attività di DJ Yoder
DJ Yoder ha commentato,
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?
Visualizza commento · Data ultimo post: 18 lug 2022 · DJ Yoder
0
Follower
2
Voti
0
Commenti
DJ Yoder ha commentato,
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.
Visualizza commento · Data ultimo post: 18 lug 2022 · DJ Yoder
0
Follower
4
Voti
0
Commenti
DJ Yoder ha commentato,
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?
Visualizza commento · Data ultimo post: 10 nov 2021 · DJ Yoder
0
Follower
3
Voti
0
Commenti
DJ Yoder ha commentato,
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.
Visualizza commento · Data ultimo post: 07 ott 2021 · DJ Yoder
0
Follower
8
Voti
0
Commenti
DJ Yoder ha commentato,
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.
Visualizza commento · Data ultimo post: 02 giu 2021 · DJ Yoder
0
Follower
2
Voti
0
Commenti
DJ Yoder ha commentato,
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
Visualizza commento · Data ultimo post: 17 feb 2021 · DJ Yoder
0
Follower
0
Voti
0
Commenti
DJ Yoder ha commentato,
+1
Visualizza commento · Data ultimo post: 08 giu 2016 · DJ Yoder
0
Follower
1
Voto
0
Commenti