All ideas
Sort by:
Trending
Status:
Showing 8941
6
VOTE
Idea / request filter on domains not just portal users
I would like to be able to filter on the idea/request email domains associated to a portal user, rather than having to pick the individual names. If I use the idea voter domains I get a list of all domains, what I would like to see is the 'Idea/re...
0
Already exists
6
VOTE
Prevent Reviewers from changing the visibility of their own ideas
All my internal users are Reviewers, as I want them to be able to see more in depth information than they can get through the idea portal. However, I don't want anyone but an Owner to be able to mark and idea as Visible to Anyone. Internal employe...
0
Future consideration
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
1
VOTE
Priority limit line should respect ranking order
I that if you drag something below a priority limit line in a prioritization list report, it pushes something else up above the line. This is unexpected behavior. If I drag a feature/record below the line, then everything else should remain below ...
0
Future consideration
2
VOTE
Ability to view and edit "people" without having to go to a capacity report
Currently the only way to edit "people" is to go to their team in the config, or via a capacity report. eg change their schedule. It would seem to make more sense to see this data in the users profile (with the correct permissions).
0
Future consideration
6
VOTE
8
VOTE
Add optional date fields or ranges on Requirements
Allow Requirements under features to have Date fields. These could be locked to the feature's date range or allowed to fall outside depending on the organization and how they manage.
This would allow for more granular reporting on Features, or t...
4
Unlikely to implement
7
VOTE
Move attachments (mockups) from feature to requirement
In the process of defining features, I create mockups and attach other files supporting the feature. Later, I'll break down the feature into product backlog items and I use requirements for that. It would be so awesome if there was a way to move a...
2
Future consideration
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