It seems that the Team sync functionality is not working as it is supposed to when there are multiple syncs within one project. For example,

Steps to Reproduce 

• Go to Jira > Teams and create the following teams.

• Alphas
• Betas
• Deltas
• Gammas

• Go to Settings > products > Sync and create a sync for each team with the same JSM project as the responder

• Alphas sync with Project 1,
• Betas sync with Project 1,
• Deltas sync with Project 1,
• Gammas sync with Project 1

• Navigate to your service and create an incident issue ABC
  In the issue view window, add a team to populate the Team field with a team from the one you created above, e.g., the Alpas team.
• Explore the operations teams and select the Alpas team.
• On the team, Navigate to this team profile and click on the Alerts tab.
• The result is the alert is not displayed in the team profile.

Now, go to the Alerts page and browse all the open alerts without filtering by a responder team.

• The result is the alert about the incident, ABC, is available.
• The Alert is created as expected but the team chosen in the issue edit view is not assigned as an Alert responder.
• When you look at the alert activity log, it shows that a different team created the alert.

The alert activity log below shows that Betas sync created the alert but in fact, the alert was supposed to be created by the Alphas sync.

Today Dec 2nd, 2024

15:5 system jira-service-management-cloud [Betas sync] ExecutionStatus[succeed] Issue comment added by System
15:52 Jira System: Alert is received with same alias. Message: "Test Sync team Alerts". Count is increased to 4
15:52 Jira System: Alert is received with same alias. Message: "Test Sync team Alerts". Count is increased to 3
15:52 System: Alert is received with same alias. Message: "Test Sync team Alerts". Count is increased to 2
15:52 Jira System: Alert created via jira-service-management-cloud[Betas sync-Create Alert] with incomingDataId[b75d5877-8275-4338-a7db-43fb69bdf3a9] with tiny id [91] id [b177d5d8-0e30-47aa-82db-ba75d7bf80fc-1733262751833]

Workaround: 

The current workaround is to add the team as an alias in extra properties.

The following community question from one of our customers is about this issue.

https://community.atlassian.com/t5/Jira-Service-Management/JSM-Operations-Syncs-for-a-project-affects-all-teams-with-syncs/qaq-p/2879457