Búsquedas recientes
No hay búsquedas recientes

BP3
Incorporación 16 abr 2021
·
Última actividad 02 abr 2024
Seguimientos
0
Seguidores
0
Actividad total
15
Votos
8
Suscripciones
5
RESUMEN DE LA ACTIVIDAD
INSIGNIAS
ARTÍCULOS
PUBLICACIONES
COMENTARIOS DE LA COMUNIDAD
COMENTARIOS DE ARTÍCULOS
RESUMEN DE LA ACTIVIDAD
Última actividad de BP3
BP3 hizo un comentario,
We are also interested in this. For us, we have customers that we interact with directly via Teams. It would be a great way to more easily move/track those customer interactions if we could create a ticket from any team's channel.
Ver comentario · Publicado 02 abr 2024 · BP3
0
Seguidores
0
Votos
0
Comentarios
BP3 hizo un comentario,
Jacob,
Your idea of the no_email tag is a great one. I used it to stop sending an email to a user that is actually a ticketing system from a customer of ours. Basically, us sending them a response was causing a loop that resulted in the systems updating each other. So I just shut it down!
While this fixed the looping updates issue for me, it did introduce another problem. That is that any users that are cc'd on the ticket no longer get emails.
The reason this happened is the trigger that sends the email doesn't have a way to break cc'd users away from the requestor.
Do you (or does anyone) have any ideas on how I can stop emails from being sent to the originator but continue to send to people on the cc line?
Ver comentario · Publicado 07 oct 2022 · BP3
0
Seguidores
0
Votos
0
Comentarios