We use the Strategic roadmap because is the only place where you can display different type of records in the timeline as bars. However we find very challenging that we need to click manually on the drop down arrow to see the related epics and use...

Since product development moves chronologically from Ideas to Features to Releases, move Releases to be after Features in the UI so the order is logical.

I would like to run an automation rule only on an update of an idea, not on creation of an idea. For some changes, it only makes sense to react to them if a a portal user (submittor) changes the value after submission, not on creation. I would lik...

We have different business groups with products in Aha and right now, everyone has to scroll through everyone else's to get to theirs. I would like to see a way for a pop-out or similar that once you hit a Product line, you get a menu of the produ...

While many To Dos are simple and can be quickly marked off. Some could be longer and do not work as "requirements. Would be nice to set a start date and end date on a To Do and perhaps spark a notification reminder to "get started".

Would be great to have a visualisation of all feature dependencies within a product. Right now the dependency visualisation exist between features, but that cannot be used to map all feature dependencies within a product.

What is the challenge? Tab advances to next field, not end date What is the impact? I have to jump from keyboard entry to mouse. Other fields cycle on tab. Describe your idea when in first date, tab should jump to end date.

I would like to be able to limit use of an extension to a set of users. For example, if I have an extension to deploy code to production, I would like to limit it so that only an ops team and team leads can trigger it.

We use Custom Tables in many workspaces to track dollar savings.Once a project reaches a certain status these committed savings should be locked. It would be a great enhancement to be able to do this with Aha!'s 'Lock based on Status' functionality.

We use master features to define use cases that require work from multiple products. The features linked to the master feature come from those different products. However, we need the ability to put requirements on a master feature to be able to t...