Automation rule to send email when reporter's email matches a certain mail server

[App Support]

Trying to setup an automation rule to send an email when the reporter's email matches a certain mail server. For instance, senders with only "@gmail.com" will receive the auto-response email. 

[Support Team [Clearvision] · Accepted solution]

Hi App Support

You should be able to do something with smart values and the text manipulation features with automation for Jira. e.g

use an if: Compare two values condition and then use smart value to compare the domain part of the email

{{issue.reporter.emailAddress.substringAfter("@")}} equals gmail.com

[App Support]

Thank you for your response. I am not familiar with Smart Values. I will look into it and check if that works.

[Support Team [Clearvision]]

No Problem,

There is a KB about smart values which is a good start:

https://support.atlassian.com/jira-software-cloud/docs/what-are-smart-values/

The rule in the UI would looks like this

[App Support]

Hi there,

Thank you! Yes I tried the same, except in the send email I selected reporter instead of initiator until the last try yesterday I included initiator along with reporter and I let it be and then I get an email notification this morning when I checked that the rule failed with an error. I am digging into that error now. Somehow I am not getting the auto-response email in my inbox though.

I will keep troubleshooting :) 

Thank you for your help!

[Support Team [Clearvision]]

Ok, Good luck!

[App Support]

Thank you. Strange but it worked with just initiator in that field. 

[Support Team [Clearvision]]

That is strange

I tested with reporter in the to field just now and that sent the email as expected

[App Support]

I will test again with just reporter in that field. 

I have been using and still using Legacy Automation. First time trying out the new Automation. 

Now I need to implement this rule to one of the rules in legacy. I was wondering if I can convert a legacy rule to a new one and then edit it using the smart values. 

[Support Team [Clearvision]]

Legacy automation is being phased out. Details are available on the following link

https://support.atlassian.com/jira-service-management-cloud/docs/what-is-legacy-automation/

You will still be able to use legacy rules but best to start using the new automation going forward. 

The legacy automation wont support smart values so you would have to create a new rule in the new automation and stop using the legacy one. I don't believe that you would be able to migrate legacy rules to new rules rather create a rule that does the same in the new rules.

The new automation is pretty powerful so anything you have achieved in legacy is most probably achievable and more

[App Support]

Yes I did notice. The new automation has more features and flexibility. And agree with you. It would be better to use the new automation moving forward. 

Thank you for your response :)