RELATED IDEAS
Allow linking of Features and Releases to a specific DevOps Iteration Level
We use a more granular structure to the Iterations in DevOps so mapping items to just the top level is not really suitable to keep a feature synchronized correctly and could involve a lot of manual changes at the beginning and end of a release.
For Example a Release should be able to be configured to be created (or linked to) an Iteration at Level 2 or Level 3 (what we would use). You can map a custom field to this level so makes sense that we should be able to automate the creation/linking via the connector.
Super annoying that this is not available. If you don't manually create and link up all the releases for the year ahead of time, you end up gettings Sprint iterations created in Aha! (which are not relevant to customers, so they have no meaning in Aha! as Release), or the Aha! releases get created as iterations in DevOps under the root iteration which is usually not the correct place.
Lots of training has to be done to Aha! users and their R&D teams to make sure the Releases in Aha! are not messed up.
I had a similar request https://big.ideas.aha.io/ideas/A-I-9166 and another that is a symptom of the release/iterations not being synced: https://big.ideas.aha.io/ideas/A-I-9692