I'm currently able to trigger automation on issue transitions when setting Flagged = 10000 as a post function to Flag the issue with Impediment. (eg. issue is sent back to development from QA in the workflow).
I can do this with the Field Value changes automation on the Flagged Field.
This properly triggers the slack notification on those specific issues that bounce back and are flagged in the JIRA workflow post function.
I'd like to also trigger another slack notification on the return path when the Flagged Field is cleared. (eg. issue comes back to QA and Impediment is cleared). There is a JIRA post function that clears the Flagged field on the way back into QA.
Is there a way to properly trigger automation when the Flagged field Impediment is cleared or is there another way to handle this scenario?
Thanks!
I figured it out!
For some reason having a custom notification event fire in the post function of the transition in question prevents the JQL from getting matched correctly in the automation rule. This might be worth checking into by the codebarrel/jira automation team.
Once I switched it to Generic Event (which essentially fires a notification to All Watchers & Current Assignee) then the rule started matching successfully.
Thanks,
-Haris V.
Hi,
What kind of field is the "Flagged field" ? If it was implemented correctly then it should trigger the field value changed trigger again.
Thanks,
Scott
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Scott,
Looks like it's a Checkboxes field with 'Impediment' as its sole option. Setting impediment on that field consists of (Flagged = 10000) on a post function which triggers the automation successfully.
On the return trip, I'm just using post function "The value of Flagged will be cleared."
P.s. This is my actual account, I accidentally posted with an integration user above.
Thanks,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.