4 ms·

> We will be reaching out via email to provide a tailored recommendation for each Opsgenie site, highlighting the best fit for your team. > Opsgenie end of sup

> We will be reaching out via email to provide a tailored recommendation for each Opsgenie site, highlighting the best fit for your team. > Opsgenie end of support – effective April 5th, 2027: A public post followed up by them reaching out individually (which takes time) along with a 2 year grace period, seems pretty reasonable?

rdsubhas 2y ago
Indeed, you are right. The title is clickbait. I'll edit.
- rat9988 2y ago
  I'm not sure it is. It looks pretty reasonable. I'm not sure about what your whole outrage is. You are a paying customer, so they have to send you an email before they do the public announcement?
  - tgv 2y ago
    Sounds reasonable. The public has little to no interest in opsgenie, but paying customers do.
  - darkwater 2y ago
    Yes, they should have done exactly that. Do you think it's ok how they managed it?
x3n0ph3n3 2y ago
My company literally _just left_ PagerDuty for OpsGenie. It's a pretty big gut punch after just doing all the work to cut over.
- lawrjone 2y ago
  This really sucks, that is rough. When you’re buying from a company like Atlassian you don’t expect this to happen really. The writing has been on the wall for a while with Opsgenie though. I work at incident.io and loads of our customers have had deprecation/migration warnings for a year or so now, pushing them away from Opsgenie and into different Atlassian products (with no migration plan, sadly). It’s been great for us as they tend to move to us (we have good migration support for Opsgenie) but confusing to watch from the outside as Atlassian never stopped selling the product even while actively shutting accounts down.
  - hkchad 2y ago
    If anyone started using OpsGenie post acquisition they should have KNOWN atlassian would change something, assuming it would remain status quo would have been naive. For us it was a seamless migration for us to Jira Service Management from OpsGenie. There were many emails, and many in app banner notifications for MONTHS. All our rules transferred over. I only had to setup our notification integrations so all links into email/slack goto Jira Service Mgmt instead of OpsGeneie. Our OpsGeneie instance is currently read only.
- tsoldrin 2y ago
  Except that nothing is going away. We did the same, migrate from PD to OpsGenie. As soon as they offered to use JSM instead, we tried it and it’s great. Only one mobile client for everything, all old OpsGenie integrations just keep running, you still have heartbeats. JSM is the same product, just integrated into Jira. If you have OpsGenie running, migrating to JSM is just the push of a button.

rdsubhas 2y ago

Indeed, you are right. The title is clickbait. I'll edit.

rat9988 2y ago
I'm not sure it is. It looks pretty reasonable. I'm not sure about what your whole outrage is. You are a paying customer, so they have to send you an email before they do the public announcement?
- tgv 2y ago
  Sounds reasonable. The public has little to no interest in opsgenie, but paying customers do.
- darkwater 2y ago
  Yes, they should have done exactly that. Do you think it's ok how they managed it?

x3n0ph3n3 2y ago

My company literally _just left_ PagerDuty for OpsGenie. It's a pretty big gut punch after just doing all the work to cut over.

lawrjone 2y ago
This really sucks, that is rough. When you’re buying from a company like Atlassian you don’t expect this to happen really. The writing has been on the wall for a while with Opsgenie though. I work at incident.io and loads of our customers have had deprecation/migration warnings for a year or so now, pushing them away from Opsgenie and into different Atlassian products (with no migration plan, sadly). It’s been great for us as they tend to move to us (we have good migration support for Opsgenie) but confusing to watch from the outside as Atlassian never stopped selling the product even while actively shutting accounts down.
- hkchad 2y ago
  If anyone started using OpsGenie post acquisition they should have KNOWN atlassian would change something, assuming it would remain status quo would have been naive. For us it was a seamless migration for us to Jira Service Management from OpsGenie. There were many emails, and many in app banner notifications for MONTHS. All our rules transferred over. I only had to setup our notification integrations so all links into email/slack goto Jira Service Mgmt instead of OpsGeneie. Our OpsGeneie instance is currently read only.
tsoldrin 2y ago
Except that nothing is going away. We did the same, migrate from PD to OpsGenie. As soon as they offered to use JSM instead, we tried it and it’s great. Only one mobile client for everything, all old OpsGenie integrations just keep running, you still have heartbeats. JSM is the same product, just integrated into Jira. If you have OpsGenie running, migrating to JSM is just the push of a button.