Problem

When a JSM service has an association to an Opsgenie team that no longer exists anywhere (not in Opsgenie, not in Atlassian Teams, not in the Merge Teams tool), the
The Jira Service Management ops REST API and The Jira Service Management ops REST API API operations hard-block, and the UI also prevents deletion and editing. This creates a circular blocking issue with no customer-facing resolution path. This is a post-Opsgenie-to-JSM Operations migration regression.

Environment

Jira Service Management Cloud any tenant that has completed the Opsgenie-to-JSM Operations consolidation and has services with stale/orphaned Opsgenie team associations where the referenced team no longer exists in any source of truth.

Steps to Reproduce

1. Have a JSM Cloud site that has completed the Opsgenie-to-JSM Operations migration
2. Identify a service with a Service Owner referencing an Opsgenie team ID that no longer exists anywhere (Opsgenie, Atlassian Teams, Merge Teams tool all confirm team not found)
3. Attempt to DELETE the service via the
   The Jira Service Management ops REST API:
    DELETE /jsm/api/{cloudId}/v1/services/{serviceId}
4. Attempt to UPDATE the service via the
   The Jira Service Management ops REST APIto clear the team association:
    PUT /jsm/api/{cloudId}/v1/services/{serviceId}Body: {"name": "ServiceName", "teamId": null}
5. Attempt to delete the service via the UI (Project > Operations > Services > select service > Delete)
6. Attempt to edit the service via the UI to clear/change the Service Owner field and save

Expected Results

• DELETE (API): The service is deleted successfully. The orphaned team association (referencing a non-existent team) is auto-cleaned as part of the delete operation.
• PUT (API): The update succeeds, allowing the customer to clear or reassign the team reference.
• UI Delete: The service is deleted successfully.
• UI Edit: The Service Owner can be cleared or changed and saved successfully.

Actual Results

• DELETE (API): Returns error:

{{ Unknown macro: { "errors"}
}}

• PUT (API): Returns 400 Bad Request
• UI Delete: Blocked with message: "[ServiceName] is currently connected to an Owner Team. To delete this service: Remove the service owner from this service and try again."
• UI Edit: Clearing the Service Owner and saving fails with: "We couldn't save your service. Check your connection and try again."

This creates a circular blocking issue: cannot delete because of team association → cannot remove team association because team doesn't exist → no resolution path available.

Workaround

(Add a workaround, if available)

Notes