Moving a Service to Another Team

Service ownership changes. Teams reorganize, a product moves to a different group. When that happens, you can move the service to another team in the same account without recreating it.

The service keeps its identity. Its integrations, integration keys, alert rules and incident history all travel with it, so the monitoring tools that send alerts to the service need no reconfiguration and keep working through the move.

Anyone who has “edit service” permission for the given teams, can perform this 

What Changes When You Move a Service

A service is owned by one team, and so are the policies it points at. An escalation policy, SLA, incident priority, task template or schedule belongs to a single team, so those references cannot travel with the service. The move asks you to choose replacements from the new team, and clears what it cannot replace.
‍

Moving a Service

Click on the team that currently owns the service. From the secondary sidebar, select the tab Services and click the service you want to move.

1. Select Move to a Different Team.
2. Select the Target Team. Only teams in the same account are listed.
3. Choose the Escalation Policy the service should use in that team. The list shows only policies belonging to the target team, so changing the target team resets this choice.
4. Choose the SLA Policy, Default Incident Priority and Task Template, or leave them empty to move without them.
5. Review the summary of what will be removed or disabled.
6. Click Complete service migration.

‍

‍

‍