OpsGenie decommission

[Robert Nichols]

So we have two OpsGenie instances.
One is linked with our JSM instance. This one is being merged and migrated to JSM and then decommissioned in a few months.
We have a separate instance though which is not connected to any JSM instance.

I can't find any information on total end of life of OpsGenie as a separate entity.

Is this a similar timeline of a few months ?

[John M]

Hi @Robert Nichols ,

John from Opsgenie support here, happy to assist!

There is no end-of-life date for Opsgenie for either standalone or JSM-subordinate Opsgenie. Both products will continue to function as normal. The merge you are referencing will not decommission Opsgenie, it will simply integrate it into the JSM interface. Standalone Opsgenie will not see any changes. 

[Charlotte Lancaster]

Hi @John M . We've had a pop-up on our instance suggesting that OpsGenie is going to turn off permanently?  Can you confirm if your message above is still the case? 

[John M]

Hi @Charlotte Lancaster 

Yes, the above is still true. If you have JSM-linked Opsgenie, it will become part of the JSM interface - so it will exist with JSM, rather than on it's own site. 

[Charlotte Lancaster]

Awesome! Thanks for the clarification John :) 

[Matthew Peel]

Hi @John M 

Thank you so much for taking the time to answer, but I'm sorry it isn't entirely clear what you mean.

The situation we are in is all Atlassian Cloud. We pay for Jira Service Management, but I believe our use of OpsGenie falls under the Free tier as I cannot find it in our admin.atlassian.com page or in our Invoices.

When I look at https://OUR_COMPANY_NAME.atlassian.net/jira/settings/products/ops/unlock, I see some UI stating "On October 17, 2024 we'll automatically start moving your operations data and configurations from Opsgenie to Jira Service Management." and "May 2025 - Opsgenie turns off permanently", which feels very End Of Life.

See below for the screenshot of what we see.

This feels very much like we have no choice in the move from OpsGenie to JSM.

If I am misunderstanding the type of OpsGenie and JSM we have, please let me know how to find out which we have so I can ask an even more informed question :) 

[John M]

Hi @Matthew Peel

I'm happy to explain. Your Opsgenie is JSM-subordinate, which means it is already considered part of the JSM product. This change will also make it part of the JSM UI.

Standalone Opsgenie is a separate product, which will not see any changes. If you are seeing that message, it means you are not on Standalone Opsgenie. 

The reason you cannot find Opsgenie is your invoices is that it is included with JSM, so it will not generate a separate invoice. 

The only way you would see an invoice for Opsgenie is if you signed up for standalone Opsgenie.

The end of life message just means the the separate UI and domain you are seeing for the JSM-subordinate Opsgenie will go away and Opsgenie will become part of the JSM UI. Your data and configurations will stay intact, they will just be moved into JSM. 

[Matthew Peel]

Much clearer, thank you @John M 

[Michael Henderson]

I saw the same message Matthew saw above in our cloud sandbox. Now Opsgenie sandbox has been migrated to JSM. But we do subscribe to Opsgenie and have an invoice. It has caused a stir for us, because we are wondering if Opsgenie will be migrated to JSM in our production environment too? The May 2025 date also has caused some consternation. It's not that we will not migrate production, we probably will. But will we have to? That's our question. 

[Dave Rosenlund _Trundl_]

As I understand things, if you have both JSM and Opsgenie (in production) THEN yes, you must migrate to the integrated (JSM + Opsgenie) solution. The deadline for getting this done is unclear (to me).

If on the other hand, you only have an Opsgenie license in production (no JSM), then you may leave things as they are. 

Care to comment, @John M ?

P.S. @Michael Henderson, It's usually not a good idea to attach your question to a thread that's older than a couple of weeks. It can be easily missed.

[Michael Henderson]

Thanks and understood. :) 

[John M]

@Michael Henderson @Dave Rosenlund _Trundl_ 

That is correct - if you are getting an invoice for Opsgenie, that means you are on Opsgenie standalone and it will not change, for now. JSM-subordinate Opsgenie is being migrated in groups into the JSM UI, so the exact dates will vary for different accounts, but you will receive advanced warnings in the app and emails about the change.  

[Cristian Blanaru]

Hi @John M 
Thank you for your detailed clarifications. Very helpful!

Could you please clarify if this might affect stand along Opsgenie in the future?

If yes, kindly suggest on our use case: we are currently using an on-premise instance of Jira Service Manager (JSM) alongside Jira and are exploring the possibility of integrating standalone Opsgenie. Could you clarify the potential implications or risks of this setup? Specifically, we’d like to understand:

• If Opsgenie can function seamlessly as a standalone solution in our environment.
• How this setup may be impacted by Atlassian’s ongoing changes, such as the separation of Opsgenie from JSM or other service modifications.
• Any considerations for future compatibility or feature loss

[John M]

Hi @Cristian Blanaru 

I wouldn't say there are any risks to integrating Opsgenie standalone with JSM, however, If you are planning on migrating to JSM Cloud at some point it would be preferable to use the Opsgenie that is fully integrated with JSM Cloud (It's part of the JSM UI, so, in this case, it's not actually a separate product called 'Opsgenie' any longer - it's just the Opsgenie features in JSM)

Here are answers to your other questions:

• If Opsgenie can function seamlessly as a standalone solution in our environment.
  • Yes, you can use Opsgenie Edge Connector to connect Opsgenie with On-Prem JSM
• How this setup may be impacted by Atlassian’s ongoing changes, such as the separation of Opsgenie from JSM or other service modifications.
  • Opsgenie won't be separate from JSM, but eventually all Opsgenie instances will be migrated to become part of a JSM instance. However, your Opsgenie will continue to work with your On-Prem JSM, even after Opsgenie is migrated to JSM.
• Any considerations for future compatibility or feature loss
  • All migrations of Opsgenie will keep data and configurations intact.

So, while you can still setup Standalone Opsgenie and use Edge Connector to link it to your On-Prem JSM, keep in mind that Standalone Opsgenie is being phased out over the next few years, so may be easier to migrate to JSM Cloud where Opsgenie will already exist. If you don't go that route, your Opsgenie standalone will eventually be migrated to JSM or Compass but it will still work with your On-Prem JSM via Opsgenie Edge Connector or Jira Edge Connector, once it's migrated to JSM.