RELATED IDEAS
Hide some basic functionality
We're starting to think there's too much functional goodness in Aha, that we could use less levels or fewer layers. Similar to how you can hide certain tabs of the the navigation, we think it could be useful to hide certain parts of the Aha data model. For example, only allowing Product Lines to have Initiatives, and disabling them on Products. Or vice-versa. Or, disabling Requirements altogether, so Features are a stand-alone thing.
We're not 100% sure what this would look like, without having actually implemented it. But, several of us feel there's too much going on at the large, Enterprise scale we are trying to implement the tool at - paring it down a bit might actually improve the usability.
-
ADMIN RESPONSESep 19, 2024
Thank you for the idea. Given the low volume of support for this idea, we do not have plans to make updates in this area at this time. As noted in the idea, it is currently possible to customize the navigation to hide features that are not used. We hope that helps!
2
MERGED
Allow admins to remove "requirements"
We have a prescribed structure in which we don't use requirements due to the restrictions on reporting. Marketing PMs continue to use them and this is causing rework/restructuring. We want to remove requirements so Marketing PMs stop using them.
0
Unlikely to implement
© 2024 Aha! Labs Inc.•All rights reserved
Agreed, I find it very confusing to disable a page in the navigation to only find out that I haven't actually disabled it but I have only hidden it in the menu drop down.
Confusing workflow: I am in workspace A which has the release gnatt chart, I toggle to workspace B that has releases disabled [b/c we aren't using releases in a helpful way yet and to see that page would be super confusing] but then it jumps to that page anyway.
We’re planning to use Aha for Epics/Features/Releases and utilize Azure DevOps for user stories (requirements) since it has more robust capabilities and is our development tool.
We’d like to disable requirements in Aha for our product line since Azure DevOps has much more robust capabilities than Aha does for requirements/user stories. Is this possible? I turned off requirements in the product line config but they still show up on the features form
I agree! We have a handful of fields built in fields that we choose not to use, but we find that Product Managers are confused by seeing them and believe they need to fill them out.
"The best don't focus on more; they focus on less and better."
Or, "Perfection is not when there is nothing left to add... it is when there is nothing left to take away."