Account settings

When changing a feature to master feature, to initiative and back (demoting), the item is recreated, resulting in a new id, and a new link. If a team is documenting the features/master features etc with links, this documentation will lose value wh...

I would like to know if there is a way to establish a scorecard for Master Features that is separate from the scorecard used for Features. We would like to use a specific scorecard at the Master Feature level such as estimated revenue, cost saving...

For auditing and documentation purposes, it would be helpful if admins could save expired broadcast messages, including a record of when they were enabled and when they were deleted. This functionality would be useful in cases where one or more us...

I like that Aha! allows me to share my product data with my organization, but I need more granular controls over who can create, read, update, and delete data. It would be great if I could create custom roles and assign them to users. Additionally...

I love Aha and I think it is worth the money we spend on it, however, there is a gap on the license model x functionalities provided that prohibits me to fully adopt it for my dev team (9 developers), eliminating Rally. The request here is to crea...

As an independent consultant, I have recommended and assisted with the set up and configuration of Aha at Several accounts. however, I can't maintain a demo set-up so I can effectively help sell the platform for you. It would also be nice, if ther...

it is not efficient when creating a product, then strategy, then release, etc. only to have a need to add a user to this effort. you have to go back to the account menu to then add to the user. I would be great if at anytime in the flow you can ad...

There needs to be another hierarchy above Product line. This hierarchy may be used as a business unit, or VP roll up. In large organizations multiple people will be using the tool to track their efforts, and not all teams will have the same proces...

Under Product Navigation, all pages in Aha are, by default, viewable except Workflow board before customization. It should also be included in the initial default.

Currently if you create a custom field of type Aha! record relationship - Products field then the values available for users of that field see the entire product hierarchy.We need to be able to filter that down to a specific Product Line and/or Pr...