Aha! data model support for actual features / components / themes, rather merely work output
Currently the "features" and "master features" relate to work output, not actual product concepts that users care about.
tl;dr; please give us more ways to separate concepts from the actual work. Features should technically be conceptual, and shou...
Guest
almost 6 years ago
in Features
0
Future consideration
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...
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...
Claire A
about 1 year ago
in Features
1
Already exists
From the Workflow view, can you add a filter or the ability to add the Feature Board Parking lot. This will help minimize the need to switch to the feature board and then back to kanban for prioritization.
Marina Reyna
almost 6 years ago
in Features
0
Future consideration
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...
Grant Smith
about 7 years ago
in Features
0
Will not implement
Our team needs an straightforward, one-click way to share feature URL's between each other. This functionality should ideally be available in all feature listings.
Guest
over 9 years ago
in Features
0
Unlikely to implement
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 ...
Guest
about 1 year ago
in Features
1
Unlikely to implement
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...
Roger Oliver
almost 5 years ago
in Features
0
Future consideration
As a Product Manager, I want the ability to clear or delete field values in bulk so that I can easily clean up errors in my data and ensure that Aha! is the definitive source of truth.
Nathaniel Collum
about 7 years ago
in Features
0
Unlikely to implement
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...
Guest
over 9 years ago
in Features
0
Unlikely to implement