for Itas dev team working with Epics makes sense, now the question is what happens when Epic and Features are assigned a release, and some of the features are done and shipped while others will move to the next release.
https://www.aha.io/support/roadmaps/strategic-roadmaps/features-and-activities/use-epics-across-releases-and-workspaces
answered, see the url and comments
https://bentleysystems1.aha.io/bookmarks/epic_by_release_gantt_roadmaps/7371793299439699759
2 release defined,
1st `22Q1 major` to be published with
Epic (Feature Done)
Epic (Feature Done and notDone)
Epic (Feature notDone)
2nd `Aha-ADO test: 2024 minor` Release Date 2024-12-09
https://big.ideas.aha.io/ideas/A-I-7852
This is currently handled by the features that are assigned to an epic. The epic itself should be assigned to the release where it will be completed, however it's features can be spread across multiple releases and delivered incrementally.