Setting notifications based on specific workflow transitions

[Kay Bickell]

I have a workflow that relies on users being able to click a button marked "Escalate" and pick their reason for doing so.  The workflow then automagically returns the case to its original state before the escalation (In Progress, On Hold etc etc).  This all works fabulously.  I have an automation which notifies the appropriate stakeholders when an escalation is made, and the reason chosen. That is also fine.

What I need to do however, is keep those stakeholders informed of the progress of that ticket once they have been informed about it the first time, and part of that, is to notify them where there are later status changes, including later escalations. And this is where I need help.

I do not want to inform the stakeholders about that item moving from to or from the escalated state itself. The reason for the escalation is important, but not that status specifically. I tried originally setting it 

           

This prevents any email being sent for a case going IN to Escalation as a status, but does not prevent it sending when the item exits the Escalation status again.

I tried at one point to put in a condition that said it could go FROM any status except Escalation TO any other status except Escalation, and that made the rule refuse to run at all.

I just need to make sure it totally ignores that hop from and to the Escalation status in the workflow and I am out of ideas.  And I know I am over my quote of "Call yourself a Jira Admin?!" questions for the week, but honestly, I am running on fumes at this point.

[Rik de Valk]

Hi @Kay Bickell , 

That seems like an interesting use case you're working on! 

I'm not a 100% clear about the requirements and your current solution. But I assume you have a field that contains the 'Stakeholder(s)' so that you can send an email to the user(s) that are stored in that field. 

For now I'll park your remark about "keeping those stakeholder informed about progress and status changes" and solely focus on the escalation-part. 

You mention that you don't want to make the actual status changes to be a trigger for notifications. So the question is: what should? If it is the Escalation reason (assuming that is a field), you might be able to use the Trigger 'Field value changed'. 

A side note: if the entire 'Escalate' status is only a hop-on-hop-off status, you could consider not using a status for that at all. Instead, use a circular transition which goes from itself to itself. Or if the escalation needs to be possible from any status, 'from Any to Itself'. 

Have a nice day! 

Rik