All ideas
Sort by:
Trending
Status:
Future consideration
Showing 6320
1
VOTE
Possibility of collapsing and thus gathering information inside folders
Who would benefit? All users of Aha! What impact would it make? It would give a better overview and gathering of information under one umbrella How should it work? My use of Aha! will be a customer database. Here I will create folders at customer ...
0
Future consideration
1
VOTE
Update/maintain link reference in whiteboard for converted workitems
Who would benefit? PM's/whiteboard users creating User Story maps, performing early-stage workshops, etc What impact would it make? Ease of use, assumed functionality How should it work? Suggested: when converting a workitem from/to eg Feature to ...
0
Future consideration
1
VOTE
Exportable list of orphaned workitems in Integrations update modal
Who would benefit? Aha admins, dev lead What impact would it make? Improved collaboration, minimizing integrations admin How should it work? Use case: I want to inform and support development team creating Azure Devops work items on Requirement le...
0
Future consideration
2
VOTE
Enhance Table of Contents to have collapsable levels
We are an ISV with hundreds of products, and we have started using Notes to centralize roadmaps for everyone in the company to view. We broke them down first by separating pages for Business Units, but even with each BU, we have many products, and...
0
Future consideration
2
VOTE
Add Variable Support to Note Templates
One feature I'd really like to see with templates is the option to insert variables into either the body or the title of the template. For example, I'd like all of my note pages created from a specific template to be named "YYYY-MM-DD Aha! Stakeho...
0
Future consideration
9
VOTE
Custom field templates rather than placeholders
We would like to see the ability to define a template for a custom field description rather than the placeholder which is there now (when editting the field, you see the placeholder, but it disappears once you start editting. Since there are no te...
2
Future consideration
11
VOTE
Limit Workspace Permissions for User with Product Line Owner Permission
We need an ability to Limit Workspace Permissions for User with Product Line Owner Permission.
Currently "Users with access to product lines also have access to their underlying products."
Use Case:
We have a number of Product Operations Worksp...
1
Future consideration
12
VOTE
Synch story point estimates between Zenhub and Aha Epics (features)
We have linked Epics (Features) in Aha with Epics in Github Enterprise, and that is working fine. however we are using Zenhub to create story point estimates within Github, and would like to be able to reflect those estimates in Aha so we can do c...
4
Future consideration
2
VOTE
Ability for a user to see what permissions they have
Our Aha! admin team frequently gets asked "Do I have a paid seat and which workspaces do I have edit permissions for". And so every time, someone from the admin team has to go take a look in the user admin area and report back. This causes an unne...
0
Future consideration
3
VOTE
