nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Opsgenie Read Only mode soon

SBACTL_JRFontanilla

Hello Everyone,

Can you give me some clarification regarding " Opsgenie Read Only mode ",
1. Is this a requirement for all users or just for specific user?
2.What specific functionalities will be restricted in read-only mode?
3.How will the read-only mode affect existing alerts

Regards
Jerry fontanilla

Accepted answers

All comments

Nayan Pandey

Hello there!

I am Nayan from the Opsgenie team, happy to help you.

Could you please help me with any article or updates that you may have received leading to this question? It'll help me answer your query better.

Awaiting your updates.

Regards,

Nayan

SBACTL_JRFontanilla

Hello,

My team received this email last january 6.

Sam Smet

Same for me, recieved that mail as well. What is happening?

Tim Westcott_3t9mnp

I also received this email for an instance that we manage.

We do not have OpsGenie added as a product subscription though.

Was this email sent in error and safe to ignore?

yaniv_c

@Nayan Pandey My team got the same email as described above with all the actions steps required. while opening the Opsgenie account there is a confirmation message which says that all alerts were moved to Jira Service Management. Please advice , do we need to perform any further steps to complete ?

Nelson Jordan

Same here. we also received this same email. What the cause of action. do we have to move

Scott Wright

Will read only still allow end-users the ability to ack alerts from the Opsgenie app?

Ian Cervantez_36fvmd

Moving forward, Atlassian expects you to create tickets in Jira Service Management to be able to start an incident (and even then, you have to navigate screens that are difficult to locate, and open up hidden context menus to actually start it).

Creating tickets to start an incident is just wild for a user experience. Because all of the custom fields in the settings that apply to "company projects" in Jira, it adds a whole bunch of mess to the process of trying to start an incident. We timed my incident response team on the new process and it took 11 minutes. Stop and try to fathom that for a second, during a critical event like a downtime situation our team is going to spend 11 minutes trying to spin up and incident and get responders on the line to resolve the issue. Just totally unacceptable, Atlassian.

Kate Clavet-D_Amelio

Hi @Scott Wright after you've completed the move and Opsgenie goes into read only, your team will need to shift to use the Jira mobile app to acknowledge alerts. Here's a link to the documentation that outlines all the steps:

https://support.atlassian.com/jira-service-management-cloud/docs/start-shifting-from-opsgenie-to-jira-service-management/

Scott Wright

How can I tell if I've completed my move? Is there something I can check?

Scott Wright

Most of our routing rules use the Details(key-value): "Opsgenie Team" as a filter for escalation. Will the field "Opsgenie Team" be mapped to JSM Team or will I have to change all routing rules to match JSM Team?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud

opsgenie

read-only