I had big hopes for moving my team to Aha and generally have been super impressed with your product. However, I won't be able to move forward due to hierarchy restrictions. My need is to break up my products on a "top-down" hierarchy, so the components are basically folders within a product, grouping sets of features that align with my sub-teams and business needs.
I first came to Aha looking for a solution where I could map out both a legacy software system I have, and plan new features on a new system I am building alongside the Legacy. So basically have all my features well documented in one tool, Aha. There is nothing else on the market that could offer this.
An essential component to my plan was to view my two systems as a User Story Map, as is described at length in this post:
However, Aha is set up so that features cannot really be categorized within a product. I see Releases as not a category of features, but rather another dimension representing chronology. In turn, you suggest throughout your knowledge center to use Custom Fields to represent components. This is awkward to me as Custom Fields I see more of like a "tag" or "label" that you'll typically see in apps like Aha, and not a true way to categorize features.
The big issue that has ultimately led me to give up my hopes of using Aha is that if I try to create a true User Story Map with just one level of hierarchy, I won't be able to categorize a more substantial User Story Map like this one. The "backbone" and "activities" are higher level of hierarchy that are missing in Aha. My hope was that using this image, I'd have basically the "user" as my product, broken down with the categories shown here as "activities" and so on.
I'm also attaching a screenshot showing how a few other tools, ProductBoard and Wrike, have deeper hierarchy, and basically "folders" under the top level where you can group features.
Would be really great if you could consider adding this ability to categorize within a product. It would be optional, and I don't see where it would cause any fundamental change in the underlying structure of Aha. With this ability to categorize in place, I'd have signed up my team!
Thank you for the consideration!
|Release time frame|
At this time, we do not have any plans to make the Aha! data model expandable or customizable beyond custom fields. However, we do offer the ability to create your own customizations to the data model via custom tables.
Thank you for sharing your experience with Aha!