Issue Summary

When a Feature has a misconfigured state mapping in the Azure DevOps (ADO) state configuration, specifically missing states that need to be created and linked to a state on Jira Align, an error occurs. The Jira Align ADO Connector logs an error: "ADO could not save the record because an ADO field rule was violated. ADO returned this message: The field 'State' contains the value 'Blocked' that is not in the list of supported values." This issue leads to the connector creating multiple items related to the split Feature.

Steps to Reproduce

1. Have a Feature on Jira Align (JA) that is syncing with Azure DevOps (ADO).
2. Ensure the state "Pending Approval" does not have a correct mapping in the connector for "Jira Align > ADO".
3. Split the Feature on JA.
4. After the split, and the failure to sync Part 2, open it and perform an update, then save.
5. Observe that a duplicate Feature is created.
6. Repeat saving on JA to create more duplicates.

Expected Results

• The Feature should sync correctly with ADO without creating duplicates.

• The state mapping should allow the Feature to be saved in ADO without errors.

Actual Results

• An error is logged: "ADO could not save the record because an ADO field rule was violated. ADO returned this message: The field 'State' contains the value 'Blocked' that is not in the list of supported values."

• Multiple duplicate Features are created in JA when updates are saved.

Workaround

1. Map the missing initial state correctly in the connector.
2. Open the original Split Part 2 that was not linked in ADO.
3. Update something on it and save.
4. This action will create a new Feature on ADO and stop subsequent duplicate Features from being created.