We have features that are mapped to a specific sprint, but within that feature, we have requirements (user stories) that could be mapped to two different sprints. The assumption with Aha! is that a feature would be completed in one sprint, which isn't always true for us. One requirement may be completed in sprint 1 and the next in sprint 2. There is the ability to create a release custom field on the requirements record, which could be a solution... but there is then no way to map that field to Azure Dev Ops.