Issue Summary

Having two PIs with the same dates and different names in the ADO iteration area may cause the Connector to use one of them.
Apparently, the Connector looks to be using the last created iteration that matches the Feature Program Increment end date based on the buffer settings.
It was confirmed that the ADO Connector doesn't support the Iteration configuration above.
However, in a case like this, it should at least inform and log into the Align TFS logs and audit log.

Steps to Reproduce

1. Create two Iterations, PI01 and PI02, in the same hierarchy level, with different names but the same dates
2. Sync a Feature from ADO with PI01
3. Update the Align Feature description, and wait until it syncs
4. Note that the ADO Feature will pick update to PI02 automatically (Expected behavior not confirmed yet)
5. No audit log messages or Logs in Align TFS application logs describing it found 2 Pis with the same date

Expected Results

The ADO Connector should detect and report this to the audit logs and Application logs.

Actual Results

No log messages presented

...

Workaround

There is a workaround, meanwhile, Jira Align doesn't support this PI configuration.
The ADO and Align admins may use slightly different dates, for example:
PI01 - from 01/Jan to 31/Dez

PI02 - From 02/Jan to 30/Dez