It would allow us to provide guidance for Master Feature creators on what sections to fill out. These sections have been agreed upon by stakeholders to make sure sufficient information is included for every instance.
Similar functionality is alre...
Have Custom Layout export views match the on-line layout as opposed to default layout
When exporting an Epic with a custom layout definition to either PNG or PDF format, the custom layout definition is not used. Instead, the default layout is used with the the Overview tab over in the right panel. Since the right panel is a narrow ...
about 3 years ago
As part of our strategic planning process, we want to prioritize all Master Features (irrespective of product line/product) in our entire portfolio. Right now, there's no way drive prioritization at this level.
We need to stack rank and prioritiz...
We follow a progression where we create Master Features and then more detailed features linked to them. We would like the ability to create a mapping and drive Master Feature status based on the status of the underlying features.
When viewing the details of an initiative (or master feature), it would be helpful to see the child-master features (or features) sorted by priority order rather than alphabetical order. That way, the child records wouldn't necessarily have to be ...
Show master features alongside features in roadmaps
Features are planned at various levels. Sometimes you need to show a mix of master features and features in a single timeline. However since master features can have features in multiple releases, it is not possible to group features by release AN...
almost 5 years ago
in Epic / Roadmaps
Capacity for teams: Ability to log time against team-based estimates
Capacity for teams is a great way to create a high level plan so that we can determine whether or not the roadmap is possible. We would like to extend it so that we can report on progress. How is it going? Are we on track?
As we were doing some training today on Aha, it occurred to me that we use the default name of "Master Feature" that Aha! provides. The term "master" as it relates to this usage has some deep negative connotations that started back with slavery. (...
We would like to keep all specs in master features and be able to push them into Trello for our Dev teams to have them on their board. Our dev teams use hello epic and organize their tasks that way so they'd be able to reference the master feature...