The History for linking and unlinking features to master features.
We need a way of identifying any scope creep by viewing the history of a master feature to see if any new features have been linked to it.
This functionality is available at a feature level as you can see all requirements that are linked to it.
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 Epics
1
Unlikely to implement
Bulk Edit "Ideas" promoting to new "Features" and linked to a single "Master Feature"
Currently, it is possible bulk edit a set of ideas and move them to individual "features" on the feature board. However, there is a use case to at the same time, link these features to a single "master feature." I cannot find a way to do this in a...
Guest
over 6 years ago
in Epics
0
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 Epics
0
Unlikely to implement
When viewing the list of features in the master features, we can see the feature name, with a link to open it, and its status. The status should be a dropdown to quickly change the status of each feature directly from the master feature.
Guest
over 6 years ago
in Epics
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
almost 7 years ago
in Epics
0
Unlikely to implement
Allowing Release IDs to be imported with Master Features
When importing multiple Master Features that are all for different products and releases it is currently not possible to specify where you want each one to go. I would like to be able to with a single import be able to say that Master Feature A go...
Guest
almost 7 years ago
in Epics
0
Future consideration
We use master features to define use cases that require work from multiple products. The features linked to the master feature come from those different products. However, we need the ability to put requirements on a master feature to be able to t...
Guest
almost 7 years ago
in Epics
0
Unlikely to implement
Hide Master Features from selection list when Master Feature has been released
When creating a feature and linking it to a Master Feature, the Master Feature selection list shows every Master Feature created. We need the option to hide/remove the display of Master Features that have been Released or Closed from this list.
Guest
almost 7 years ago
in Epics
0
Already exists
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
about 7 years ago
in Epics
2
Unlikely to implement