Trigger notification when issue type changes from epic to anything else

[Casey Enderlein]

Hello - I need to create an auto-trigger notification 'if the issue type field value changes from Epic to any other issue type value'. Can you share guidelines on this?

To start, I have 'when: value changes for issue type', however when reviewing 'if' conditions I am not seeing where I can go from here. I know how to create the 'then send notification', so just needing to filling the middle of the rule with correct logic. Thanks in advance.

[Trudy Claspill]

Hello @Casey Enderlein 

Welcome to the Atlassian community.

With the Field Value Changed trigger you have access to the original and new value for the changed field through the {{fieldChange}} smart value.

You could use a {{smart values}} Condition to check the former value and current value of Issue Type for the trigger issue. You can learn more about the fieldChange smart value here:

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--fieldChange--

Use one condition to check if the former value was Epic.

Then you can use a regular Field Value condition to check that the current issue type is not Epic.

Then add an action to send the email.

[Casey Enderlein]

Thanks for your feedback, Trudy. In reviewing the article you shared, I am a bit unclear onw where I would add the smart values to check previous VS new issue type values (if a change was made). Here is a screenshot of what I have setup currently, and is not working. 

[Trudy Claspill]

You have to use the {{fieldChange}} smart value. This is a special smart value available only when you use the Field Value Changed trigger.

An excellent testing and debugging tool is the Log action. You can use that to write out data to the Audit Log when the rule runs. Here is a test rule I did, triggered by a change of Issue Type, and just writing out the information available from the {{fieldChange}} smart value.

You can see in the Audit Log that the "from" and "to" attributes have the original and new issue type IDs while the "fromString" and "toString" have the original and new issue type names.

So you can use {{fieldChange.fromString}} in a comparison to see if the original issue type of the issue  was Epic. 

As an added measure you can add a Issue Fields condition to confirm that the new issue type is not Epic, though I'm unsure how you could change an Epic to an Epic.

[Casey Enderlein]

ahh i see, now it is clicking! thank you so much for your help this worked.

[Trudy Claspill]

Great!

If my responses helped you resolve your requirement, please consider clicking on the Accept Answer button above my responses to mark your Question as Solved.

[Bharat Kalia]

Hi @Casey Enderlein - Welcome to the community. It seems like you might be able to achieve this with the help of 2 automations and they will look something like below - 

1. Trigger - Issue created and issue type = EPIC. Action - just add a label to the EPIC ticket. 

( This rule will make sure you know which issues were EPIC when the issue type has been changed).

2. Trigger - Field value changes on Issue type and condition "issue type is not equal to EPIC" and also add labels in ("whatever label that was added in create in the first rule") 

Action - Send notification and also remove the label from the ticket that is no longer EPIC. 

I hope this will solve the problem and only touch issues which are moved from EPIC to some other issue type. 

Thanks,

Bharat

[Casey Enderlein]

Thanks for your feedback Bharat! Unfortunately, this setup is sending a notification any time the issue type field changes (no matter the starting issue type value), however we only desire for a notification to be sent if the issue type changes from starting value of 'epic' to any other issue type value.

[Bharat Kalia]

hi @Casey Enderlein - Did you put in a condition to check the issue that it sends a notification for should be "epic". The label will fix this problem I guess.