All ideas
Sort by:
Trending
Status:
Future consideration
Showing 6036
5
VOTE
Don't show the option to download videos in a shared KB
What is the challenge? Some customers with a private knowledge base do not want their users downloading videos. What is the impact? Allowing users to download content increases the likelihood that is shared with users who shouldn't have access to ...
0
Future consideration
7
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
13
VOTE
Create parent-child relationships when converting whiteboard objects
It would be helpful and add efficiencies to be able to select multiple whiteboard objects and convert to parent/child records based on the connectors. For example, I may start planning my goals and initiatives in a whiteboard and then add multiple...
0
Future consideration
5
VOTE
Display capacity line on Releases when looking at Epics board view
What is the challenge? When viewing the Epics on a board view, a capacity line does not appear even when "Epics" or "Features and epics" are used for the calculation. What is the impact? When estimation is done at the epic level, and epics are use...
0
Future consideration
10
VOTE
Include Belongs To in record link reporting
Who would benefit? All teams who create parent-child relationships What impact would it make? It would help teams who are using record link reporting to validate data relationships How should it work? In the attached example, a feature belongs to ...
2
Future consideration
2
VOTE
OpenAPI / swagger document
What is the challenge? The API documentation lacks some accuracy and is incomplete What is the impact? Even if Aha!`s support is always helping out, when i have strange API questions, a complete openapi / swagger document would be helpful Describe...
1
Future consideration
5
VOTE
Roll up named range estimates to parent records
I use named ranges for adding t-shirt size estimates to my epics. I want to roll these estimates up across epics to the associated initiative so I can easily understand the effort and costs of the full initiative.
This roll-up works for other sce...
0
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
7
VOTE
Ability to send objects backwards/forwards in whiteboards instead of just to the front or to the back when layering multiple objects
Who would benefit? All Whiteboards users What impact would it make? This would enable users to easily order layered objects, which is particularly applicable when creating wireframes in the tool How should it work? Right now users can bring an obj...
1
Future consideration
16
VOTE
Manual Sending of Requirements to integrated development tool
Presently, there isn't a way to have requirements in a draft status like there are with features. This tends to be somewhat problematic when you have multiple requirements types you work with e.g. subtasks and user stories. It will automatically s...
2
Future consideration