There are several scenarios where features are pushed to future releases after dev effort started or put on-hold and addressed later. The current starter view shows expands the release start and end dates to the earliest start of a feature and latest finish of a feature in that release. This makes it look as if the releases are very long and overlapping in an illogical manner.
NFV BU PLMs want to use the starter roadmap, but unable to use it due to this discrepancy.
In the attached file you can see the above explained scenario. I do consider this as a fix rather than enhancement though.
Thank you for the idea. Releases in Aha! are time-boxed containers for the features within them, so in a timeline view the release will always expand to fit the features within it. In a situation where development started on a feature prior to the previous release's release date, this will cause overlap in the releases, but will also provide an accurate view of when the work is being done.
In the situation of development being put on hold, if the feature is moved to the new start date, the release start date can then be adjusted accordingly.