Features
Sort by:
Trending
Filter by:
Status
Showing 1180 of 8937
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
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
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
1
VOTE
Option to reflect Prioritization Rank in other areas of the platform
Who would benefit? Product Managers using Prioritization functionality as well as the feature board What impact would it make? It would reduce the time and administrative burden with feature prioritization while improving consistency across the pl...
1
Already exists
3
VOTE
5
VOTE
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
Record Links in Feature History
When a feature has a record link created to it that ties it to another feature, there is the Record Links section which shows the dependencies (depends on, contains, etc.)
Well, it doesn't appear that we can see who has linked what records to what...
1
Future consideration