Maintenance after migration

Maintenance policies in Opsgenie were previously managed as a policy. After migration, maintenance is now a standalone feature in Jira Service Management and Compass, allowing users to manage maintenance plans more efficiently at both the global and team levels.

Migration summary

Is maintenance available in all Jira Service Management and Compass plans?

Yes, maintenance is available across all plans with no loss of functionality.

Is maintenance automatically migrated?

Yes, all existing maintenance policies from Opsgenie are automatically synced to Jira Service Management and Compass.

Are there required actions for full workflow parity?

No, maintenance is mapped directly to Jira Service Management and Compass without requiring manual reconfiguration or workarounds.

Maintenance in Jira Service Management

In Jira Service Management, maintenance is now a standalone feature rather than being categorized as a policy. It can be managed at both the global level and the team level.

• Global maintenance plans can be configured from Operations > General configuration > Maintenance.

• Team-based maintenance plans can be managed within each team’s operations.

All previously configured maintenance policies from Opsgenie are fully migrated, and the functionality remains unchanged. You can continue creating maintenance plans as they did before.

Read more about maintenance in operations.

Maintenance in Compass

Maintenance in Compass follows the same structure as Jira Service Management. It is now managed as a dedicated feature rather than a policy.

• Global maintenance plans can be configured from Operations > General configuration > Maintenance.

• Team-based maintenance plans can be configured at the team level.

All existing maintenance plans from Opsgenie are automatically migrated, and no additional setup is required. You can continue using maintenance plans in Compass the same way you did in Opsgenie.