As PM I should have direct visibility to changing a Release Date, so I understand why I can't make the Release Date dependent on Milestone dates. However, I would like to be alerted anytime a Milestone that my release is dependent on, is scheduled to continue after the designated Release Date. If the system isn't going to update the release date automatically, I need some trigger to remind me to review / push out the release date.
Thank you for the idea. This is possible today by enabling delivery risks. The status of this idea was out of date. You can learn more here: Manage Risk
I am adding my comments from the idea that was merged.
Today, for releases, you can only have dependencies can attach to release phases, milestones, and features. Please add the release date to that list. The benefit is to align a RTM and create a dependencies for market campaign, internal/external communications and so on that are part of GTM which can occurring after the RTM.
Agree in principal. I would prefer to have my release date made variable based upon a set dependency (as with the ability to link dependencies on phases or milestones. However, for those who prefer to have a firm release date regardless, I concur that there needs to be some type of an alerting function which notifies the product owner the release date is now impacted in some way.