RELATED IDEAS
Merged idea
This idea has been merged into another idea.
To comment or vote on this idea, please visit APP-I-2568 Initiative dates should be based on linked features, not releases.
Drive initiative dates by contained requirements rather than releases
Merged
I would like the Initiative start and end date be driven by the underlying master features and features rather than the releases that contains the MF/F.
Today if a development team moves a MF/F from one release to another, we need to manually update that it is a new release that contains the MF/F and link it to the Epic, If the MF/F controlled the initiative the change of release wouldn't matter
-
ADMIN RESPONSEJan 20, 2020
Thank you for the idea!
You can set dates manually, or automatically based on release dates. We provide this automatic setting to be on the release level (rather than features) as this would generally require much less configuration (when considering the number of features vs. releases).
While we understand your use case, based on current priorities and community feedback, we are unlikely to make updates in this area in the near term. To avoid manually setting dates, we would suggest linking them at the release level.
However, we will continue to monitor the parent idea for overall community feedback.
© 2024 Aha! Labs Inc.•All rights reserved