All ideas
Sort by:
Trending
Status:
Unlikely to implement
Showing 1378
1
VOTE
Allow extending aha.auth for building new importers
Who would benefit? Users of Aha! Develop who build custom exporters What impact would it make? Right now, it is unclear how to build an exporter with regards to authentication. The aha.auth API only supports authentication with services for which ...
0
Unlikely to implement
1
VOTE
Add Todo item ~ close (x) broken
Who would benefit? All users (on iPads?) What impact would it make? Improve usability, fix broken functionality How should it work? X in upper right of modal should close/cancel Add user flow.In fact, better yet, fix that and add a Cancel button
4
Unlikely to implement
7
VOTE
Create a separate record for acceptance criteria
I'm new to Aha, and contacted support to ask about recording acceptance criteria. There suggest was to use a template in the 'feature' for both he story & the AC, which to be fair does work. But in the same way we can link requirements to a fe...
1
Unlikely to implement
8
VOTE
Paid Seat Transparency Across Aha! API
When calling get-all-users in the API we receive the field “paid_seat”. This field is not included in any other get-user calls inside the API, not specific user, or user by product. This is a problem. In February we had around 500 hundred users. W...
1
Unlikely to implement
8
VOTE
Master Feature release should be automatically established from Feature release info (i.e. inherit the last of the due dates of the features)
It is extremely inconvenient and the cause of much manual reconciliation that the Master Feature release (and date) isn't *automatically* established as the latest of the related Feature releases (and dates).
So can the Master Feature release rele...
1
Unlikely to implement
10
VOTE
Update status of requirements on status change of feature
I don't want to change the status of each and every requirement individually when changing the status of a feature. For example, when I hand off a feature - which has 5 requirements, for example - to engineering to spike, they come back with a ful...
4
Unlikely to implement
8
VOTE
Quick way to reference existing Personas within Features and Requirements.
As a product manager, every day I am creating a new initiative (less often), feature and requirement. In the writing of User Stories, whether it's a feature or a requirement in Aha!, best practice is to mention the person for which the feature wil...
3
Unlikely to implement
2
VOTE
10
VOTE
Display release theme on feature board
The feature board shows a column for each release, but unless you name the releases to be identifiable (I use release versions), then it's hard to quickly see the theme of each release. It would be good to have the option of displaying the release...
0
Unlikely to implement
8
VOTE
Increase the maximum number of slides/pages in a notebook beyond 40
We have a large organization with multiple divisions under using Aha!. Need to create a single Notebook that can host all Roadmaps for specific division for easy access. Limit of 40 is very low. Need this to be in 80-100 range.
0
Unlikely to implement
© 2024 Aha! Labs Inc.•All rights reserved