All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5653
9
VOTE
Option to avoid forced formatting of certain fields (e.g. tag fields) in Aha Pivot Reports
Reports out of Aha would look a lot more stylish if the forced formatting of certain fields could be avoided. Namely the colorful boxes around all the 'Tags Fields' (predefined and editable). This adds unccessary clutter to the reports and cannot ...
2
Future consideration
7
VOTE
Add functionality to workflow to change states based on fields
There are certain fields that we would like to have populated before an Initiative can move from one state to another (however, it is not required upon entry or not known upon new entry of an Initiative). Therefore, as the Initiative progresses vi...
1
Future consideration
6
VOTE
forcing portal users to rank ideas
portal users can obviously vote on any idea but there needs to be a feature that forces them to rank/prioritize the ideas they have voted on so they get to play their own product manager and make the tough calls on which of their ideas is most imp...
2
Future consideration
4
VOTE
2
VOTE
Whiteboard diagram key that updates shapes automatically
Use case: When I create a workflow diagram, I have repetitive shapes representing specific steps (i.e. process, decision, database, ...). If I decide to change the colour or style of a step, I need to select all the same step shapes and change the...
0
Future consideration
4
VOTE
Control which fields a Develop user can update in a record in a Roadmaps workspace
Currently when an Aha! Roadmaps record is assigned to a Develop team that gives anyone with contributor permissions in the Develop team access to edit any field on the record (even those in the Roadmaps layout). I'd like a way to control this more...
1
Future consideration
4
VOTE
Pivot Chart: Expandable Rows / Group by Rows
When you create Pivot you would like to have totals per groups and be able to expand 2nd level columns to see further detail. If I have a PivotTable which is showing information on Epic Level, I would like to expand this column so that I can see t...
0
Future consideration
9
VOTE
Terminology customizations should persist throughout all screens when cascaded from Account level
We have updated some terminology for all of our products to use “Feature” (instead of default Master Feature), “Epic” (instead of default Feature) and “Story” (instead of default Requirement).
Unfortunately, this update in terminology isn’t consis...
0
Future consideration
4
VOTE
9
VOTE
Release Phase Dates Determined by all related records
My last idea around being able to adjust Release Phase dates was rejected but our release phases are static (Closed Beta, Open Beta, GA) so simply adding another random phase isn't an option. This level of standardization is needed as we have very...
1
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved