Búsquedas recientes
No hay búsquedas recientes

DJ Yoder
Incorporación 15 abr 2021
·
Última actividad 18 jul 2022
VP, Customer Support Upland Software, Inc. uplandsoftware.com
Seguimientos
0
Seguidores
0
Actividad total
34
Votos
10
Suscripciones
17
RESUMEN DE LA ACTIVIDAD
INSIGNIAS
ARTÍCULOS
PUBLICACIONES
COMENTARIOS DE LA COMUNIDAD
COMENTARIOS DE ARTÍCULOS
RESUMEN DE LA ACTIVIDAD
Última actividad de DJ Yoder
DJ Yoder hizo un comentario,
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?
Ver comentario · Publicado 18 jul 2022 · DJ Yoder
0
Seguidores
2
Votos
0
Comentarios
DJ Yoder hizo un comentario,
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.
Ver comentario · Publicado 18 jul 2022 · DJ Yoder
0
Seguidores
4
Votos
0
Comentarios
DJ Yoder hizo un comentario,
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?
Ver comentario · Publicado 10 nov 2021 · DJ Yoder
0
Seguidores
3
Votos
0
Comentarios
DJ Yoder hizo un comentario,
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.
Ver comentario · Publicado 07 oct 2021 · DJ Yoder
0
Seguidores
8
Votos
0
Comentarios
DJ Yoder hizo un comentario,
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.
Ver comentario · Publicado 02 jun 2021 · DJ Yoder
0
Seguidores
2
Votos
0
Comentarios
DJ Yoder hizo un comentario,
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
Ver comentario · Publicado 17 feb 2021 · DJ Yoder
0
Seguidores
0
Votos
0
Comentarios
DJ Yoder hizo un comentario,
+1
Ver comentario · Publicado 08 jun 2016 · DJ Yoder
0
Seguidores
1
Voto
0
Comentarios