Email with Automation for Jira is broken after 30th June 2021

[Gerardo Dalena]

Hello,

we have a P1 ticket running from 3 days, but Atlassian support have yet to give us an answer, so I'm starting to search a workaround.

We have a set of rules with Automation for Jira that sends mail notifications to update several stakeholders about our issues. After 30th June, so after the email address has changed from noreply@automationforjira.com to no-reply@automation.atlassian.com, the rules are broken. So, if the rule says to send the email

• to: a
• cc: b, c, d, e

what happens is that that the mail is sent

• to: random address between a, b, c, d, e,
• cc: all other address, except a random one is missing

So in the end, there is always one stakeholder that do not receive mails.

I've tried to edit some rules, to put all the address in cc, and tried to edit the TO field other address or the "Reporter", but there is always something missing.

Any suggestion and workaround is welcome.

Thanks,

[Carlos Faddul · Accepted solution]

@Gerardo Dalena

In this case, I can suggest three options:

1. Send to everyone in "cc", than make an automation define who will and who will not receive
2. If you use Jira Service Management, I can suggest that you include stakeholders in the request participants field and trigger a daily email (I use a similar rule with just over 60 people in copy in the email) and so far it has not been a problem.
3. Using Smart values, populate a custom field in any transition to get the emails, then use this custom field "aaaa@gmail, bbbb@gmail.com, cccc@gmail.com" (but this option is very error-prone since you would need to populate the field correctly.)

I hope you were able to give you some alternative

[Gerardo Dalena]

Hello Carlos,

tried the first one for a few hours, it worked for 90% of the cases, still a great success for me considering the previous days. Thank you so much! In the end, Atlassian fixed the problem.

[Carlos Faddul]

Hello @Gerardo Dalena 

Can you explain more about how the atlassian fix the problem. Maybe in the future i will need something similar :)

[Gerardo Dalena]

Hello,

I opened a support request and Atlassia fixed this issue on their side, I don't know the details. Well, actually they pull out a workaround, as the main bug is still opened JRACLOUD-76955

Best regards,