RELATED IDEAS
Allow disabling the automatic feature status updates based on requirement status while keeping the feature progress calculation based on requirement completion
we sometimes add user stories to a feature after other ones have been completed, for example feature is to deliver a piece of functionality and we create a spike, and then that may get closed before we add all the other user stories needed to complete the feature
© 2024 Aha! Labs Inc.•All rights reserved
I came across this idea and looks like it can be disabled as per the answer provided by Aha admin. https://big.ideas.aha.io/ideas/APP-I-5842
Aha epic (feature) should not close just because all imported Jira stories under the same in Aha have been closed. This causes issues in Aha and Jira epic status sync. Aha epic is closed out even when its corresponding Jira epic is still open or in progress. There should be an option to disable this auto update setting. Even if we plan our epics in Jira properly with all user stories in them, there still can be a chance when we need to add more stories based on unavoidable scenarios, so enforcing to close the Aha epics is not the right way.
I need this for my teams; our process is "tasks all closed by QA --> Story resolved" then a product owner reviews the story and either closes it or reopens it if there is a problem. This then repeats at the level up, i.e. "Stories all closed by PO --> Feature resolved" where the product manager then knows they need to review the feature and sign off on it by closing it.