Schedule or Escalation Policy with name already exists in JSM Operations

Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.

Summary

Learn why you can't reuse the name of an On-Call Schedule or Escalation Policy after deleting the Team associated with it.

When attempting to reuse the name, you get the error:

We couldn't create the escalation policy
Escalation with [name] already exists.

Teams are soft-deleted

When you delete an Atlassian Team used in JSM Operations, the associated On-Call Schedule and Escalation Policy are also deleted. However, these items are only soft deleted, and you can still restore them within 30 days.

Because they are not permanently deleted yet, you can't create a new Schedule or Escalation Policy using the same name during this period.

Reuse the name immediately

Reactivating the deleted team and renaming or deleting the Schedule or Escalation Policy allows immediate reuse of the previous name. So, to reuse a name right away:

  1. Restore the deleted Team.
    1. After you delete a team, all team members and the org admin will receive an email on how to reactivate limited team information within 30 days.
    2. Use the link to reactivate on the email to restore the team. 
  2. Rename or delete the Schedule or Escalation Policy using the relevant name.
  3. Delete the Team again.
Last modified on Jan 17, 2025

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.