Ricerche recenti
Nessuna ricerca recente

BP3
Data ingresso 16 apr 2021
·
Ultima attività 02 apr 2024
Seguiti
0
Follower
0
Attività totali
15
Voti
8
Abbonamenti
5
PANORAMICA ATTIVITÀ
BADGE
ARTICOLI
POST
COMMENTI NELLA COMMUNITY
COMMENTI AGLI ARTICOLI
PANORAMICA ATTIVITÀ
Ultima attività di BP3
BP3 ha commentato,
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.
Visualizza commento · Data ultimo post: 02 apr 2024 · BP3
0
Follower
0
Voti
0
Commenti
BP3 ha commentato,
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?
Visualizza commento · Data ultimo post: 07 ott 2022 · BP3
0
Follower
0
Voti
0
Commenti