Map to iterations paths within Azure Devops
When syncing from a new board to DevOps for the first time, new iterations are being created regardless if they already exist.As such, it would be beneficial to map releases from Stories On Board to pre-existing iterations in DevOps to avoid
For example, if there is an iteration in DevOps with the same name as a release in SoB, lets say "Release 1", when syncing it will create a new iteration in DevOps called "Release 1 - 1". Then you have to move items from this new iteration to the correct one and delete the newly created iteration.
I appreciate there maybe a use case for not doing this mapping automatically, but having this option would help minimise re-work within DevOps & allow better control of where the work items are going.
Open to the community to suggest workarounds :)