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.

  • Suzanne Vaughan
  • Nov 19 2014
  • Planning to implement
Release time frame
  • Attach files
  • Guest commented
    August 05, 2015 06:50

    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.

  • A Bp commented
    21 Jun 18:00

    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!