Couple of questions around timing of the auto-enroll step:
Can we disable parts of OpsGenie from being moved over during auto-enroll or turn off auto-enroll all together? We want JSM feature to be there but only use OpsGenie as a reference point to add configurations as needed otherwise I see this getting really messy.
Basically we would like to avoid duplicate resources being made that confuses people. For instance OpsTeam1 already exists in Jira, OpsTeam1 also exists in OpsGenie and the end result that we seen during testing is that Jira will wind up with 2 Teams names OpsTeam1 which is not ideal. Is there a preferred way to merge Teams with the same name in Jira and OpsGenie?
Will this result in duplicate alerts and notifications when the auto-enroll happens? These things will be defined in OG and JSM at the same time for the same people so obviously want to avoid lots of spam.
Hi @Shaun Pinney How will this affect the mobile app for Opsgenie, is this moved to the Jira App? Most of our on-call agents use the mobile App to acknowledge an alert.
1. It is not possible to move certain features as all opsgenie features based on your plan will be synced with Jira Service Management.
To answer your problem of duplicate teams, all your opsgenie teams that have been moved over will have the opsgenie logo, so that you can identify which is your operations enabled team ( see example below of how teams moved from opsgenie will be highlighted with a logo)
2. This will not lead to duplicate alerts or notifications. You will see all configurations and data is synced , we are not duplicating anything.
Hence you get an alert(which can be seen in both products) -> notification is sent for that alert depending on responder rules set up.
You acknowledge the alert from Jira Service Management , it shows acknowledged in opsgenie and also the responders get 1 notification for this action if set up or vice versa. Hope this helps!
@Shaun Pinney We’ve noticed that the new Jira app no longer includes a Zoom link option on incident requests. This prevents stakeholders and on-call team members from easily joining Zoom calls when alerted away from their laptops. The only workaround is to switch to desktop mode in a mobile browser, manually copying the URL from SMS or email alerts, which causes confusion for those who already have the app installed. Any fix planned ??
The Conference Calls and Chat Tools features for Incident Management have recently been moved to the Premium and Enterprise plans. If you're on the Free or Standard plan, you might not have access to these features. You can upgrade your plan to take advantage of all the advanced capabilities it offers.
@Himanshi Gaba On the Enterprise license of JSM, there's an issue where the Zoom link is missing from the issue view in the app. When accessing the issue via a URL on a phone, it defaults to opening in the app. However, when opened through the app, the Zoom link is not visible. This functionality was present in the previous version of the app before the update. It's puzzling how this oversight occurred on Atlassian's part.
Opsgenie was a more centralized approach and easy for teams to go to and navigate. We are cross functional and the UI for JSM Ops is extremely convoulated it feels. Is there or will there be a centralized landing page? Currently things are so nested it is not user friendly
Atlassian Team members are employees working across the company in a wide variety of roles.
December 10, 2024 edited
Thanks a lot for your feedback @Aaron Jorgensen . We recommend the Your Work page or the Teams page to be the central point for you to kickstart Ops. In addition to the above entry points, we are also working on improving our navigation flows on JSM (Currently in EAP), which will enable you to go through the flow more smoothly with all Operations related aspects under a single menu in the navigation. We expect this to be live soon as well, which we hope will further improve your experience.
Having said that, we are always looking for opportunities to improve, and so looking forward to any additional inputs and few more specifics around the JSM Ops UI being convoluted.
Looks like we had our automigration roll out. At least one team (my team) had an issue with two schedules migrating (a primary on-call and a secondary on-call); they seem to have been smashed together to create one incorrect schedule.
Everything in OpsGenie is still correct.
I see the option to export schedules in OpsGenie and Jira, but no way to import schedules. What's the easy fix here?
116 comments