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.

  • Max Cascone
  • Feb 14 2017
  • Likely to implement
Release time frame
  • Attach files
  • Max Cascone commented
    February 27, 2017 20:52

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

  • Zac Gery commented
    June 08, 2017 19:06

    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.

  • Andrew Ingraham commented
    05 Mar 04:04

    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