Issue Summary

When a user is removed from an Atlassian/Operations Team, residual team membership entries are not fully cleaned up. As a result, alerts continue to be routed to users who are no longer members of the team.

Steps to Reproduce

(The behaviour might not be replicable on-demand)

• Create or identify an existing  Atlassian/Operations Team and add User A as a team member.
• Configure an alerting/routing setup that sends alerts to this team (e.g., escalation policy, routing rule, or notification rule targeting the team).
• Trigger an alert and confirm that User A receives notifications as expected.
• Remove User A from the Atlassian/Operations Team (using the standard UI / team management flow).
• Trigger another alert that targets the same team.
• Observe the users who receive the alert.

Expected Results

• After User A is removed from the Atlassian/Operations Team, User A should no longer receive any alerts routed to that team.

Actual Results

• User A, who was previously removed from the Atlassian/Operations Team, continues to receive alerts that are routed to the team.

Workaround

For each affected user who continues to receive alerts after being removed from a team:

• Re‑add the user to the affected Atlassian/Operations Team.
• Manually remove the user from the team again via the standard team management UI.
• Confirm that the user no longer appears in the team membership and no longer receives alerts when new alerts are routed to that team.