Hello,
I have an automation configured that will ping a Microsoft Teams Channel when a value changes for a custom field named "Engaged Team" (When: Value changes for Engaged Team > Engaged Team = [value] > Then: Send Microsoft Teams message). This helps our teams with escalations.
The automation(s) work great when I change the value of the Engaged Team custom field from the view issue screen. However, when I change the value from a transition screen, the automation doesn't work. In fact, the automation isn't being triggered at all as there is no entry in the automation logs.
What's weird is that I have another automation that pings Microsoft Teams when an issue is assigned and whenever I change that field from a transition screen, the automation works. So it seems as though the issue is isolated to the custom field "Engaged Team" or the Trigger "When: Value change." By the way, I could understand if the automation didn't work perfectly if both fields were changed on the same transition screen. That was not the case on my test. All I did was change one or the other.
Does anyone have any ideas/suggestions? Thank you in advance for your assistance.
Hello @Ted Korba
In the trigger, what do you have for the For Operations field, where the example below shows "Edit Issue"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Trudy Claspill ,
I see where you are going here. I added "Transition Issue" to the For field and problem solved!
Thank you for your help!
Regards,
Ted
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ted Korba
Can you have another automation with the trigger 'When issue transitioned' and configure the same way as the 'When value changed' automation rule and try?
Select the from and to statuses where the transition screen is displayed.
Thanks,
Vamsi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Vamsi Kandala ,
Thanks for the response. I guess I didn't do it that way originally because sometimes agents might change the Engaged Team field without actually transitioning to a different status.
I will give that a try and get back to you.
Regards,
Ted
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ted Korba ,
I understand.
I just wanted to check whether this automation rule works and if so, you can have both rules in place.
Please try and let us know how it went.
Thanks,
Vamsi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Vamsi Kandala ,
I attempted to create that automation but ran into a couple of potential problems:
Thanks again for you help.
Regards,
Ted
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.