Application
Sort by:
Trending
Status:
Showing 7570
111
VOTE
Aha user management (groups, "mail to" communications, etc)
I would like to manage a large group of users (mostly commenters and reviewers) with some additional user management tools including: 1 - user groups - the ability to create groups of users and then assign product permission, workflow board visibi...
13
Future consideration
6
VOTE
Install new fonts for Knowledge Base
What is the challenge? We would like to use a Knowledge Base for external user access; however, without the ability to use our branded font, it is a challenge What is the impact? Misalignment with branding materials Describe your idea We would lik...
0
Future consideration
12
VOTE
Dependency roadmap as a standard view
Who would benefit? Users that: need to track upstream work they are dependent on need to understand downstream work that is dependent on their work need to easily identify delivery risks based on dependencies What impact would it make? A roadmap i...
0
Future consideration
3
VOTE
Request to holistically omit Parking Lot releases in filters for all Views
What is the challenge? Add Release as a filter in every view to only select "Active" releases and omit Parking Lot "Inactive" releases. What is the impact? This creates a lot of manual work on all of our views. Cannot leverage the Auto Add new rel...
1
Future consideration
4
VOTE
Allow resizing report columns without visible headers
What is the challenge? When cell headers and column headers are hidden in a pivot, it is not possible to drag and resize the columns themselves. What is the impact? There are certain scenarios where having visible headers is redundant or unneeded,...
0
Future consideration
63
VOTE
Indicate required fields when editing a record
We need the ability to make standard and custom fields mandatory for existing records.
When a record is being edited, the UI should flag empty required fields so that the user is prompted to update them. This will help us ensure that critical inf...
12
Future consideration
57
VOTE
Add option to drive Feature progress % by the feature status
The progress % on a feature should be in sync with the status of the feature. When the status changes so should the progress %. Using to-dos, requirements, or estimates to drive the feature progress % isn't an option for us as different groups may...
18
Future consideration
10
VOTE
Allow Release Date (internal) and Release End date (date range) to sync
Who would benefit? The Release date (internal) drives many of the OOTB reporting functionality in Aha! so it must be maintained and accurate for reporting to be accurate. For many teams, the end date of the release and the Release date (internal) ...
1
Future consideration
71
VOTE
Control which personas & competitors should be inherited and which not
At the moment all personas & competitors are inherited from the levels above even if some do not apply. In order to avoid duplication by defining the same persona/competitor over and over at the product level it would be much better if persona...
4
Future consideration
8
VOTE
Ability to Configure Epic View as Default for all workspace views (Board / Prioritization)
Who would benefit? Enterprises who maintain Epic only or use Epic as primary record type. What impact would it make? Reduce confusion. The teams are currently directed to feature view on the board and prioritization view by default. Per Aha concie...
0
Future consideration