Add a new idea Subscribe
Status Unlikely to implement
Categories Features
Created by Mark D
Created on May 24, 2017

RELATED IDEAS

Master Feature release should be automatically established from Feature release info (i.e. inherit the last of the due dates of the features)

It is extremely inconvenient and the cause of much manual reconciliation that the Master Feature release (and date) isn't *automatically* established as the latest of the related Feature releases (and dates).

So can the Master Feature release release be automatically established? (by using the latest of the associated Feature releases)

  • ADMIN RESPONSE
    Aug 22, 2019

    Thank you for your idea. It is now possible to view master features and their features on the starter roadmap. By default, this new view will also show a release date milestone for each master feature and feature included in the roadmap. Checkout this blog post for more details.

    While this will not update the release of master features automatically, it should make it easier to spot and correct discrepancies.

    While we can see value in master features automatically updating based on the releases of their features, there are some complexities which prevent it. In particular, master features can have features included from other products. In this case, changing the master feature's release would also move it to a new product.

    Given the potential confusion this would cause, and the new capabilities on the starter roadmap, we are unlikely to implement this idea. We hope you can understand.

  • Attach files
  • Maury H
    Reply
    |     Dec 26, 2018

    Here's a real world Use Case to (hopefully) help explain the need for this feature better:  A Manager is in planning session and determines a Master Feature will need to move out from Release 3 to Release 4, so the Manager drags the Master Feature to Release 4.  The Scrum teams are unaware of the change unless the Manager either a) manually moves each related Epics at the same time they move the Master Feature (while holding up the planning session) or b) remember to send a communication to someone else so THEY can manually move the Epics (and adjust any Sprints) in order to remain in sync.