RELATED IDEAS
This idea has been merged into another idea. To comment or vote on this idea, please visit A-I-8964 Add 2-way integration mapping for release start and end dates.
Allow bidirectional or from integration start date for releases - Aha<>VSTS
Merged
Right now the only choice is one way start date from Aha. This caused me major havoc during my integration.
We are at the early stages of Aha adoption. We have features mapped successful. We have also attempted to enable release mapping. but we had issues – you can’t set the start date to be bi-directional. As a result, we ended up resetting all of our iteration start dates in ADO when we did the import. As a result, our development team is very reluctant to re-enable this.
The reality is – release planning happens primarily in the development team as opposed to the product team since the contention is always around the people – and the people in question are the development engineers who fall under development management. Therefore, the release planning starts life in the development world, not the product world. It seems it would work better for us if the release start and end dates were on way but set in Azure DevOps.