Have ability to select which Features move with a Master Feature
Currently, when moving a Master Feature, there is the ability to move ALL related Features with it or move none of the related Features. Would be helpful to be able to granularly select which Features to move with a Master Feature.
cheryl fetchko
about 6 years ago
in Epic
0
Unlikely to implement
There are times when a Master Feature gets released into multiple Releases. It would be nice to see the master feature and all the releases associated with it form the Gantt Chart.
Guest
about 5 years ago
in Epic
2
Unlikely to implement
Apply filters to the Milestone Chart View and keep milestones off the chart until explicitly charted
We have a long list of master features for our product line that need to be prioritized at that level. It would be helpful to do it iteratively, and one way to do that is with filters that allow us to focus just on the master features associated w...
Guest
over 5 years ago
in Epic
0
Unlikely to implement
The Prefix for all Master Features is 'E', this is a suggestion to change this globally to M to align with the default terminology.
EG PRODUCT-E-123 should be PRODUCT-M-123 instead.
Guest
over 5 years ago
in Epic
1
Unlikely to implement
Add the ability to customize Master Feature cards on the Master Features Road Map
The Master Features Road Map does a great job of showing what master features we are working on in each release and the why. The why being the goals and initiatives they support. Those releases are organized by external due dates and show nicely. ...
Guest
over 6 years ago
in Epic
0
Unlikely to implement
Under Reports / Roadmap / Features
in customize view we select "show master features" as we want to show both master features and features
we can add filter on feature tags : this works fine
but if we add filter on master tags for e.g. : it isn't...
Agnes Muller
over 6 years ago
in Epic
0
Unlikely to implement
Visually represent the size of a feature with larger or smaller cards
In Aha, it's difficult to represent the relative effort required for different master features and features. Time is not the only consideration. For example, so features have dependencies that while not requiring heavy effort, will effect the dura...
Nate Dunlevy
over 6 years ago
in Epic
1
Unlikely to implement
We have 20+ people in Contributor role working on the same Product. All of them have by design access to bulk actions and can inadvertably bulk delete all of the hundreds of items that we have in Aha!. We want to somehow restrict access to bulk ac...
Guest
over 6 years ago
in Epic
0
Unlikely to implement
The customer success team suggested I just use initiatives for user journeys and master features for user journey steps, which is a good temporary fix. However, defining a user journey is a pretty specific thing that I think should be set apart fr...
Mike Mitchell
almost 7 years ago
in Epic
2
Unlikely to implement