Recherches récentes
Pas de recherche récente

BP3
Adhésion le 16 avr. 2021
·
Dernière activité le 02 avr. 2024
Suivis
0
Abonnés
0
Activité totale
15
Votes
8
Abonnements
5
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par BP3
BP3 a ajouté un commentaire,
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.
Afficher le commentaire · Publication le 02 avr. 2024 · BP3
0
Abonnés
0
Votes
0
Commentaire
BP3 a ajouté un commentaire,
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?
Afficher le commentaire · Publication le 07 oct. 2022 · BP3
0
Abonnés
0
Votes
0
Commentaire