All ideas
Sort by:
Trending
Status:
Unlikely to implement
Showing 9235
13
VOTE
"Start numbering at" or "Continue numbering" option for ordered lists
What is the challenge? We currently have no way to set the beginning number of an ordered list What is the impact? Limited options for intersplicing media in step lists, broken lists Describe your idea Just need a "Start numbering at" or "Continue...
1
Future consideration
3
VOTE
Propagate Epic status change to linked Features
What is the challenge? Change in Epic status not reflected in associated Features What is the impact? Lack of status sync between Epic & Features Describe your idea We leverage Epic as the primary record for approval workflow. I would like to ...
0
Already exists
6
VOTE
110
VOTE
Enhanced Powerpoint Support
As much as we all hate to admit it, Powerpoint is still the defacto presentation tool, and it does provide some powerful diagramming tools that would be difficult to replicate.
I hate having to copy Aha views into Powerpoint, and the reverse isn't...
5
Future consideration
24
VOTE
4
VOTE
View time in status on feature card
What is the challenge? I use time in status a lot now that it is available. One thing I have had to create is multiple reports that show time in current status when looking at feature aging. I'd love to be able to display that on the card directly...
0
Future consideration
6
VOTE
Optimize resizing and autofit in presentations
What is the challenge? When adding large Aha! views (such as custom roadmaps) to a presentation slide, it’s difficult to resize them appropriately to fit within the slide. This leads to inconsistent results with the resizing and display of views. ...
0
Future consideration
7
VOTE
Chrome extension to capture feedback from anywhere
What is the challenge? We work in many applications and Aha! cannot build custom integrations for all of them. This makes it very hard to users of those applications to capture feedback and store it all in Aha! ideas. What is the impact? Lost feed...
0
Future consideration
6
VOTE
Option to not copy Requirements when Copying a Feature
What is the challenge? We have begun tracking high-level Requirement information in Aha! and have seen that when we copy a feature the stories are also copied. This may be appropriate in some cases, but not all. What is the impact? This may create...
1
Future consideration
62
VOTE
Report on a value's historic values
Enable the user to report on the values of a field based on its history. maybe a calculated field property where you indicate the field and the version back for that field. History(Custom_Field1,1) would show the value of that field one change bac...
6
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved