Teams after migration
Opsgenie teams transition to Atlassian Teams, which function across Jira Service Management. While most team structures remain similar, there are key differences in permissions, role management, and team visibility. Review these changes to ensure a smooth transition.
Migration summary
Are teams available in all Jira Service Management plans?
Yes, teams are supported in all Jira Service Management plans. However, team management functions now follow Atlassian’s organization-wide team structure rather than Opsgenie’s site-specific settings. Read more about Atlassian teams.
Are teams auto-synced after migration?
Yes, all Opsgenie teams are automatically migrated to Atlassian Teams, which are used across Jira Service Management and other Atlassian products.
Are there required actions for full workflow parity?
No. But here are some changes you should be aware of:
The Opsgenie Team Admin role transforms as Operations Admin of the team (Opsgenie Admins are transformed as Operations Global Admins). Team settings are managed centrally by Atlassian teams.
Team names, descriptions, and members are now global across all Atlassian products and can be reviewed by other teams.
Teams in Jira Service Management
In Jira Service Management, teams are now managed as Atlassian Teams but retain their operational configurations within Teams > Operations. Read more about launching team operations in Jira Service Management.
Team management is controlled at the Atlassian platform level. Opsgenie teams are automatically migrated as Atlassian teams where the Operations are automatically enabled. You can reach your team’s configurations from Teams > Operations.
Your teams will be visible beyond Jira Service Management to other Atlassian products, as Atlassian teams are a global entity.
Any Jira Service Management agent can launch the operations for an Atlassian team unless restricted.
Was this helpful?