Jira Connector: Synchronizing Stories from Jira that are associated to a team that doesn't exist in Jira Align causes invalid updates (custom team mapping)

Issue Summary

When customers configure multiple boards on one Jira project & Jira Align custom team mapping (organization field). There is an issue when there is a team on the Jira (custom field context) but doesn't exist in Jira Align. When a story syncs from Jira with a foreign team to Jira Align this will cause the team field to update with a team that does exist in Jira Align along with removing the feature when the associated feature updated (adding a PI).

Steps to Reproduce

Make sure you have a project and board(s) configure to bi-directionally sync features and stories
Create a custom team field in Jira for a project that has multiple boards associated (single select list)
Make sure the custom team field has a team that doesn't exist in Jira Align added as a drop down value
Next, configure the custom team mapping in Jira Align (organization field)
Create a feature A that has a story from team A (exist in Jira Align and on the custom team mapping within the same Jira Project)
Next, create a story in Jira associated with Team B (doesn't exist in Jira Align)
Next, when the story syncs to Jira Align associate that story to Feature A which was previously created
Note: now Feature A should have 2 stories associated. 1 for Team A and one with Team B.
Next, update the features PI from unassigned to a current or future PI
Next, check the Stoy associated with Team B and navigate to the audit log

Expected Results

PM will need to help define expect results for this logic. Ideally, we should possibly have some type of guardrail to prevent this from happing.

Actual Results

• Team is updated from Team B to Team
• Feature is removed from the story

Workaround

The workaround is to add the team unknown team to the Jira Align program, map the board & team to Jira Align, add the team to the Jira Align custom team mapping (organization) or remove the unknown team from the Jira Custom team field context to prevent this from happening.