RELATED IDEAS
Configure so that epics and feature dates are following release dates
I would like to be able to configure so that the master features (MF) and features (F) follows the release date. This would be very helpful during sprint planning and replanning. The bulk editing is a work around, but still when you move around the MF and F you need to bulk edit over and over and there is a risk that some changes are being forgotten.
-
ADMIN RESPONSEJul 22, 2022
Thank you for your idea. Feature dates are currently independent of the release date. This is intentional as often times these dates should not match up. One suggestion here would be to use the gantt chart or starter roadmap when moving features from one release to another. This would then update the feature dates according to their position on the timeline.
At this time based on the explanation and option above, we are unlikely to implement this idea. We hope you can understand.
4
MERGED
Auto-populate feature start/end dates when allocated to release
Some of our product teams are more “agile” that others. That meaning, Features are likely to be dragged between releases as opposed to having their start/end dates updated. it would be great for us if we could automatically set the start/end date ...
0
Unlikely to implement
© 2024 Aha! Labs Inc.•All rights reserved
This is important because the association of features and epics to a release is dynamic and can change often based on so many considerations. The most convenient way to move features and epics across releases is via the feature board. But in order to automatically generate a roadmap view or presentation, dates must be set accordingly, and this doesn't happen. The current state is very cumbersome. We effectively can't generate roadmap views or presentations as a result.