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

Thanks for following up, Michael! I just took a look at that idea, and I believe it can be reopened, so that we can continue to track status there. I appreciate you letting us know.

Awesome to see this shipped and not only offered through Ent+...I submitted idea A-I-9728, which was merged into this idea. Part my my idea is to allow this configuration/automation at any level of the hierarchy and furthermore ability to make in inheritable at parent levels. e.g. Feature to Release, Release to Initiative, Initiative to Goals.... Is this something that is still being considered or should I enter a new Idea?

This should happen so that the feature set is consistent between Requirements-> Features and Epics! Support just told me it doesnt exist and I was disappointed.

I am using Aha! to auto update status of parents in my Azure DevOps environment to lower the updates my managers have to do, so this would be great to have.

Yes, please!
Ideally it could be toggled for those that don't want it but for us it was an assumed capability. I pestered the fine folks in Support to determine that it wasn't a defect but a yet to be implemented feature.

1000000% agreed!

This is also really important, and key, for us - very surprised it doesn't exist in some capacity today

It's a "MUST have" feature IMHO.

This would be a very nice addition, and I'm actually surprised Aha! doesn't support it already. It makes things very manual.

Completely agree with the ability to override if nessary.

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?  

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.  

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

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

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.

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!

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).

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

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.

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.

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.