Master feature status should automatically get updated based on the feature status

I'd like to see my master feature status automatically updated as my features get updated. So, if a feature is in progress, the master feature status should show in progress. After all features are ready to ship, the master feature should update to ready to ship automatically, and later on after they are all shipped the master feature should close the loop by updating the idea's status.
Also, the feature board should show the features that belongs to a master feature somehow grouped together per release...

  • Paulo Branco
  • Apr 12 2017
  • Future consideration
Release time frame
  • Attach files
  • David Hegarty commented
    May 05, 2017 13:52

    Yes, please do this. Both ideas in this are needed. I have started using master features extensively, to track features that need to be sent to individual teams. At the moment I have to update every one by hand - this makes them not very usable.

    also, when I change the order of a master feature, I need a way to somehow be able to change the order on the feature board. Right now it's a nightmare trying to keep them in sync.

  • Joe Andreana commented
    July 06, 2017 13:19

    This would be tremendous if we can have this functionality. It will allow us to have proper reporting to our executives.

  • Katie Besgen commented
    November 15, 2017 21:45

    I completely agree with updating the Master Feature Status to In Progress once a Feature is set to In Progress and similarly Shipped when all features are Shipped.

  • Peter Makover commented
    December 22, 2017 17:34

    Yes this would be a big improvement and there is already precedent in the way the Start/End dates behave where the dates on the Master Feature is automatically updated based on its children Features' dates.

  • Peter Makover commented
    December 22, 2017 17:37

    A further thought - it would be even better if the business logic behind how the Master Feature status is automatically updated could be configured.  For example, one use may want the Master Feature status to be set to In Progress as soon as the first child Feature is set to In Progress, but another user may only want the Master Feature status to update once ALL child Features are set to In Progress.

  • doug evans commented
    May 22, 2018 22:13

    I second the suggestion to make this configurable. That would be awesome!

  • Puneet Singhal commented
    August 28, 2018 21:37

    Applies to any parent container (master feature, Initiative, even goal)

    Update status automatically to In Progress, and also save the Start date and Finish Date (when status changes to Closed).

    + I'd prefer if the MasterFeature progress can be rolled-up from constituent features (# SP completed DIV Total SPs).

  • Jordan Walter commented
    January 08, 2019 16:06

    This would be really beneficial for our workflow. We use Master Features to track a majority of our work. With the way this currently functions a lot of our work will need to be done manually, and add a lot of wasted effort. Please implement this!

  • Guest commented
    March 19, 2019 11:02

    Yes please otherwise our JIRA workflow becomes difficult to keep in sync. Plus the AHA! roadmaps and reports can then be used and work as expected.

  • Preksha Patel commented
    April 18, 2019 20:45

    Without this functionality reporting automatically is not possible and product managers are chasing status manually, causing status reports to be error prone.

  • Guest commented
    October 24, 2019 18:20

    100% agree - We're using master features, too, and without this functionality, reporting ends up being a very manual process.

  • adam doxtader commented
    October 25, 2019 13:57

    For us, data quality in Aha is of paramount importance because our entire company relies on it for organizational awareness and launch planning.  And we use Master Features a lot.  The ability to automatically set the state of a master feature based on its underlying features' states, eliminates the need of Product Managers or Program Managers to manage the states manually which, let's face it, is not what PM or PgM's should have to worry about or focus on.   By implementing this functionality you allow us fully leverage a Jira-Aha integration and which maps features to epics, which then would update master features appropriately, removing the reliance on manually maintained data, which is error-prone and leads to inaccurate data.  

  • Scott Shultz commented
    17 Feb 21:24

    We are hitting this as well. We use Master Features to communicate the "big deliverables" to executive management. I've been pushing product managers to be sure to always connect Features to Master Features, but if everyone has to go manually edit status in Master Features what's the point?  

  • Julius Tancinco commented
    28 Feb 18:15

    Completely agree with the ability to override if nessary.