All Opsgenie questions questions, answers, and comments

Re: Re: How to get JSM Ops Critical alerts to override An...

Yura — Fri, 10 Apr 2026 01:03:42 GMT

Nice one, On vanilla Android pixel it's Settings -> Modes -> Do Not Disturb -> Apps -> Selected App -> Tap Gear icon next to selected Apps -> Add apps -> Jira

Re: Migration to Jia Inquiry

Kaushik from Spike_sh — Thu, 09 Apr 2026 11:44:42 GMT

For migration assistance, your best starting point is Atlassian's official migration guide for OpsGenie to JSM Operations. https://support.atlassian.com/jira-service-management-cloud/docs/start-shifting-from-opsgenie-to-jira-service-management/

You can also reach out to Atlassian Support directly — they have a dedicated migration team that can walk you through what changes. The key things that typically change: the UI moves into Jira, alert routing rules get restructured, and some API endpoints change. Your integrations, schedules, and escalation policies should carry over, but it's worth auditing them post-migration.

Costs also significantly change. I would highly suggest you to search for Jira Service Management Pricing Breakdown.

- Kaushik (Spike.sh)

Re: email intetgrations keep opsgenie.net domain

Kaushik from Spike_sh — Thu, 09 Apr 2026 11:40:10 GMT

Great question, and an important one to sort out before your OpsGenie instance goes away. The opsgenie.net email domains are tied to the legacy OpsGenie infrastructure, and Atlassian has stated they will eventually be retired as part of the JSM Operations migration.

You might have to recreate your email integrations with the new jsmalerts.atlassian.net domain sooner rather than later. I think it's also safer to do these manually instead of relying on the migration wizard

- Kaushik from Spike.sh

Re: How to manage alerts in jira mobile app instead of op...

Kaushik from Spike_sh — Thu, 09 Apr 2026 11:33:08 GMT

In the Jira Cloud mobile app, alerts are under: Menu → Operations (or JSM Operations). You may need to enable the Operations feature in your JSM project settings first. From there you can view, acknowledge, and close alerts.

I hope this helps, lmk.

- Kaushik from Spike

Re: Disable Twillio

Andy Rusnak — Wed, 08 Apr 2026 21:41:44 GMT

Hi @Thijs Geurten ,

Welcome to the Atlassian Community! When you say that you are trying to disable the "Twillio integration", what specifically do you mean?

For example, are you trying to disable an Integration like what is mentioned here to trigger alerts?
Or are you trying to use a different service to send SMS/Voice notifications to alerted users?

Best,

Andy

Disable Twillio

Thijs Geurten — Tue, 07 Apr 2026 09:21:24 GMT

WE need to use a phone number via our PBX and need to disable the Twillio integration. I have admin rights but are unable to switch the Twillio integration off. Any suggestions how to fix this?

Re: Re: alert_policy & notification_policy return 403 err...

Sandra Herlufsen — Wed, 01 Apr 2026 06:55:47 GMT

It was actually a problem from JSM. They didn't provide the correct permissions with the api token. They fixed it and it is now working.

https://jira.atlassian.com/browse/JSDCLOUD-18653

Re: Escalations are not Firing on Alerts in my Free Account

Ramavath suresh — Mon, 30 Mar 2026 08:12:03 GMT

Open 👐

Re: Re: email intetgrations keep opsgenie.net domain

Scot Wilson — Sun, 29 Mar 2026 21:22:36 GMT

G'day all, it's Scot from the Opsgenie Support team here.
That's pretty close @Benjamin & @Hai Le !

When you migrate from Opsgenie to Jira Service Management, your existing email integrations @<instance>.opsgenie.net will continue to work until April 2027. You can turn off/shutdown the Opsgenie UI once you've migrated to Jira Service Management and this won't affect your email or API integrations until April 2027.

Any new email integrations you create after you migrate will use the the JSM specific email suffix/domain.

One note: If you ever change your atlassian.net site's url, this will cascade through to your legacy Opsgenie email integrations and you'll have 90 days to switch to the new suffix/domain, and these opsgenie.net email addresses will work til 2027.

Hope that adds a helps,
Scot.

Re: email intetgrations keep opsgenie.net domain

Benjamin — Sun, 29 Mar 2026 05:06:41 GMT

Hi @Hai Le ,

Welcome. The domains are shifting to Atlassian.net. So likely, once your OPsgenie instance is destroyed, it's all atlassian.net from there. The opsgenie.net domain will retire sometime in 2027 that was the last announcement.

Thanks,

Ben

Re: Unable to parse fields in incident rule

Arkadiusz Wroblewski — Sat, 28 Mar 2026 12:48:10 GMT

Hello and welcome to the Community @Shreya Karnelli

By default, Opsgenie uses the email subject as the alert message and the email body as the description. If the incoming email is HTML, Opsgenie also attaches the original email. So the subject prefix, the disclaimer/footer in the description, and the HTML attachment part are not something I would try to solve in the incident rule first.

I would move that logic into the Email integration under Advanced settings -> Create alert. That is the place where Opsgenie supports parsing and transforming email content. For priority, the parsed result must resolve to P1-P5. If not, Opsgenie falls back to P3, which matches what you are seeing.

So my first question would be: are you still using the default Email integration mapping, or have you already customized the Create alert action there?

Unable to parse fields in incident rule

Shreya Karnelli — Sat, 28 Mar 2026 00:22:41 GMT

Hi Team,

We tried creating incident using incident rule and email alert integration.

We are facing the following issues.

1. Unable to parse and choose from email subject line. In email we use "new incident reported - " in the beginning of subject line which cannot be removed here. so it has created incident with the same subject line.

2. Unable to parse and choose specific fields from email body. See for example in the following incident description we have fields marked in red which are unnecessary.

3. Unable to set priority by choosing a particular field from email body.

We would like to get in contact with the Opsgenie support for assistance and discuss the issues and know if anything can be done about this.

email intetgrations keep opsgenie.net domain

Hai Le — Fri, 27 Mar 2026 17:52:23 GMT

After migration from OpsGenie to JSM Operations, all email integrations migrated over with the existing "opsgenie.net" domain. My question is will this domain stay around even after our OpsGenie instance is destroyed or do we have to create new email integrations with the new "jsmalerts.atlassian.net" domain?

Re: Regarding opsgenie alerts

Nayan Pandey — Thu, 26 Mar 2026 11:40:30 GMT

Hello Ishant,

Thank you for reaching out to Opsgenie Community. I am Nayan from Atlassian Support happy to help.

You can achieve this with Opsgenie using Notification Rules on the user profile.

Configure the on‑call user’s Notification Rules
Each on‑call engineer configures their own rules under Profile → Notifications:

a) Add a high‑priority “New alert” rule for P1
– Condition: Priority = P1
– Notification methods: Voice call to their mobile (immediately)

This will ensure that whenever a P1 alert is created and routed to the on‑call schedule, the person currently on‑call gets a phone call.

b) Add another condition for everything else:
– Condition: “Match all alerts” or Priority < P1
– Notification methods: Push notification (immediately)

Rules are evaluated top‑down, so ensure the P1 rule is above the catch‑all rule. That way, only your critical P1 (e.g. MDL load failure) alerts trigger a voice call, and lower‑priority alerts remain as push notifications only. More detail on configuring notification preferences is here: Create and manage notification preferences | Opsgenie | Atlassian Support

If you'd like to do this for certain users, you can create a custom role for them and create a Central Notification Template as well.

I hope the information provided is helpful.

Regards,
Nayan

Regarding opsgenie alerts

Ishant Kalra — Wed, 25 Mar 2026 09:34:41 GMT

Is there a way in Opsgenie to configure Notification Rules so that when a specific alert (e.g., a P1 MDL Load Failure) is triggered, the person currently on-call receives an immediate voice call to their mobile phone, while lower-priority alerts remain as standard push notifications?

Re: Re: Migration to Jia Inquiry

Nikola Perisic — Tue, 24 Mar 2026 10:55:33 GMT

@Mohammad Itani

You can see these articles: https://support.atlassian.com/jira-service-management-cloud/docs/start-shifting-from-opsgenie-to-jira-service-management/

https://www.atlassian.com/software/opsgenie/migration

There are all answers to your questions detailed on these links.

Re: Migration to Jia Inquiry

Mohammad Itani — Tue, 24 Mar 2026 10:53:02 GMT

there is a request to migrate opsgenie to Jira.

I want to check what will change if we did the migration, like cost, schedules ...etc.

Re: Migration to Jia Inquiry

Nikola Perisic — Tue, 24 Mar 2026 10:48:41 GMT

Hello @Mohammad Itani

Are you migrating from one system to Jira?
Are you migrating from Jira data center to Jira cloud?
Are you migrating from Jira cloud to cloud?

Migration to Jia Inquiry

Mohammad Itani — Tue, 24 Mar 2026 10:29:12 GMT

Hello,

can you please let me know who can I contact to assist us in understanding what could change after I migrate to Jira.

Thank you

Re: Unable to login to Opsgenie... This started 3.17.26

Mirek — Sat, 21 Mar 2026 10:18:13 GMT

Welcome @Rick White

You’re still within the official support window (Opsgenie isn’t scheduled to fully shut down until April 2027), so this isn’t an early retirement..

There’s is also no official widespread login outage or bug right now for Opsgenie.. the service itself is up and running normally according to status tracking. It’s more likely the login problems you’re seeing are tied to account‑level access, provisioning, or configuration issues rather than a known global bug.

Please review Atlassian Admin to confirm user status and product access, check SSO/SCIM provisioning for sync issues, and look for any recent org-level or billing changes that may have affected access