Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

BP3
Beigetreten 16. Apr. 2021
·
Letzte Aktivität 02. Apr. 2024
Folge ich
0
Follower
0
Gesamtaktivitäten
15
Stimmen
8
Abonnements
5
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von BP3
BP3 hat einen Kommentar hinterlassen
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.
Kommentar anzeigen · Gepostet 02. Apr. 2024 · BP3
0
Follower
0
Stimmen
0
Kommentare
BP3 hat einen Kommentar hinterlassen
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?
Kommentar anzeigen · Gepostet 07. Okt. 2022 · BP3
0
Follower
0
Stimmen
0
Kommentare