-
-
Notifications
You must be signed in to change notification settings - Fork 437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpsGenie becoming Jira Service Management #1272
Comments
Can you show any proof of this mandatory transition? I still see Opsgenie legacy URLs without any move requirement. I also found this reddit post which favors your point your making here. It is definitely apparent that Atlassian is taking the service over now. To keep this backwards compatible, i think i'll need to create a new plugin since the old one still works as is. It looks like it requires quite a subsantial change, (new account, admin privelges added and possibly more to work through the new Jira Service? Perhaps i need a Thoughts/Advice? |
I started a PR, if you could test it out for me, that would be amazing 🙏 |
I think you should just keep Opsgenie as is and add a Jira Service Management plugin separately. In all honesty I'm a little confused about the transition and we are working through a few things with Atlassian support. This is the doc that is supposed to answer all questions. This doc details how OpsGenie will become 'read only' at some point. For our account in particular we see this banner on OpsGenie: I'll try my best to test, but we actually don't use apprise directly, we are a client of @PrefectHQ and Prefect uses apprise for notifications, I'm just trying to connect the dots here so we can be ready when our OpsGenie instance goes read only. Tagging a few people from Prefect here @robfreedy @EmilRex . This also relates to prefect issue #15906 |
📢 OpsGenie Clients Must Migrate to Jira Service Management
🔗 In February OpsGenie becomes read only and alerts will be managed through JSM
💡 Anything else?
I believe the API works the same as the OpsGenie api, the only difference is that the endpoint changes to an Atlassian endpoint
The text was updated successfully, but these errors were encountered: