Updates to sending Incident Stakeholder Comms and reporting emails in Opsgenie

[#1]

Hi Opsgenie Community, 

Starting on February 1, 2024, Google launched new email protection requirements so we are implementing two changes to ensure secure delivery of emails you send.

Stakeholders now need to be verified to receive Incident Stakeholder emails

Previously, unverified users in Opsgenie could be added as a stakeholder to receive emails on incidents as part of Incident Stakeholder Comms.

Now, unverified users can still be added as a stakeholder in Incident Stakeholder Comms, but only verified users will receive emails on incidents.

This change has gone live as of November 24, 2023. There is no change to the verification process. Emails with an Atlassian profile will be auto-verified, and emails without an Atlassian profile will need to accept an email invite to get verified. To learn more about working in Opsgenie as a stakeholder, please read our Opsgenie support article.

Users can only send reporting emails to their own email addresses

In Reporting & Analytics in Opsgenie, you could previously schedule a report to be sent to any email address.

Now, you can only enter your own email address and can only send reports to yourself.

This change has gone live as of November 24, 2023, for all Opsgenie and Jira Service Management customers and you can find an example below of the new experience:

This is now the default so there is no action required on your part. If you had existing automated reports that sent to someone that is not yourself, they have been removed so you will need to share the email you send to yourself with the relevant parties if you would like to share reports with other parties.

Please refer to our support documentation to learn about reporting terminology and capabilities. 

Questions?

Please comment questions below and the team will jump in to answer. 

Sincerely,

The Jira Service Management and Opsgenie Teams