Features
Sort by:
Trending
Status:
Showing 1196
3
VOTE
Assign individuals to work using % allocations
We need an ability to assign one or more individuals to an Aha! record and indicate that their capacity is partially allocated to that record. For example, initiative A is estimated at 1,700 hours and assigned to Team A. User A on the team is assi...
0
Future consideration
5
VOTE
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
6
VOTE
Show which release a feature is assigned to in the master feature details slide-out
When planning master features/epics, I need to see which releases the master feature spans across by seeing which releases the sub-features are assigned to. This information would be displayed in a third column in the feature list on the master fe...
0
Will not implement
8
VOTE
1
VOTE
Automatically create new copy features in other workspaces based on feature tags
Who would benefit? Any product owner that has multiple workspaces or multiple tiers of workspaces. What impact would it make? Reduce the amount of work by creating tickets once instead of copying and moving. Further, changes in the feature in one ...
1
Unlikely to implement
4
VOTE
Allow a change in Feature Rank to trigger Automation
Aha currently provides no good way for us to be aware of when the Rank changes. Knowing what the current Rank isn't good enough. I realize this can be seen in Feature History. But, it isn't feasible to have to regularly check the History of all Fe...
0
Future consideration
6
VOTE
8
VOTE
Feature board containing different filter-based lists for backlog management
Combine the List filtering capabilities with the feature board's management capabilities: so I have a board, but instead of moving around in explicit releases for a single product, I can define "feature groups" based on filters (like the List fitl...
0
Unlikely to implement
7
VOTE
As a user I don't want my requirements sent to JIRA (or other integrations) if they're marked as Will not implement
I often mark requirements as "will not implement" in Aha (rather than deleting them) just to keep a trail of requirements we've discussed but decided aren't needed. Then when I push to JIRA from Aha, it brings all requirements for a feature over.....
1
Will not implement
© 2024 Aha! Labs Inc.•All rights reserved