Operations Global Admins Can't modify Teams?

[Gary Spross]

We are in the process of performing our migration from Opsgenie to JSM Operations. With the migration, Opsgenie teams become Atlassian teams. That's great. Love the consistency of using the same team type throughout all of the apps.

The problem however, is the level to which team management is restricted. According to this documentation, only team members or org admins can manage and make changes to a team. No in between.

Users with the Operations Global Admin role should be able to manage and make changes to operations enabled teams. Currently, the admins would either have to join the team (by adding themselves when creating the team or asking a member or org admin to add them to an existing team) or the team would have to be "open". Neither are great options...

Are there plans to add the ability for Operations Global Admins to be able to admin operations teams?

[Calvin]

We also have this problem, I had to add myself into Opsgenie teams before the migration so that I could manage them once they've been onboarded. Its actually created some funny issues like users asking me (the admin) to help them manage their set up and me having to tell them I can't unless they give me permission.

Problem is a bit more compounded when the Team admin leaves and their account is deactivated and now we have ghost teams with schedules I can't remove until I hear back from our Org admin.

[Michael Henderson]

Wow! We have a stand alone version of Opsgenie and our plans are to migrate in 2026. I am glad you all brought this up. I will either have to prep for this or hope that Atlassian will mitigate the issue as requested.