RELATED IDEAS
Ability to mark phases and milestones as completed (without creating to-dos)
For the phases, it would be very helpful for Program Management to be able to acknowledge that a phase has completed and allow for the establishment of a baseline like (estimated date) and actual date. That would include the planned release date too.
Using Features as a workaround doesn’t seem very straightforward, especially in light of all the features that are true features not wanting to impact any of the Product Management features, epics and related work associated with the release.
Looking for a view of the Release Plan for these milestones and all the associated ‘to-dos' for those phases and milestones.
-
ADMIN RESPONSEAug 7, 2019
Great news! It is now possible to track progress on goals, initiatives, releases, release phases, master features, and features. The percent completed can be entered manually or automatically calculated based on related records and can be visualized using progress bars on roadmaps.
Check out the blog post for more details.
© 2024 Aha! Labs Inc.•All rights reserved
I need the ability to mark MILESTONES as completed.
This request was specifically for phases and milestones. Since this hasn't been implemented it should not have been closed. Please see my similar idea that I resubmitted recently. Milestones need to have the ability to have a completed status.
This is exactly what we need! Please implement.
Very much would like to see the ability to see the date a milestone or phase is initially planned to be both started and completed, and when in reality the phase both starts and ends, and report against that as a way to see how PM's are getting on with evaluating their resources, time it takes to actually complete initiatives, and so on. This would really help my particular team!
Thanks!
With this feature it would be useful to have capacity planning at a phase level. i.e. if features are assigned to a phase you want to do your capacity planning at that level as well as report your progress on that phase (via the burn down chart). The only way to get around this currently is to use sub releases and master release at the product family level, which is quite clunky as it adversely effects burn down charts due to the release date being the same for each sub-release.