Option to hide goals and initiatives from selection on the Master Feature, Feature or Release
I would like the ability to mark a goal or initiative as complete/obsolete so that they are not available for selection on the Master Feature, Feature or Release. I know that you can do this via Archive, but the issue with this is on the reporting...
Amy Lackas
about 6 years ago
in Epics
1
Already exists
Currently, the user can link a feature to a master feature by searching by feature id. However, the user is unable to link a master deature by searching by master feature id. This creates an inconsistent user experience
Keith Davenport
over 6 years ago
in Epics
3
Future consideration
Bug: If your epic layout has Status but not Team you don't see the status. You can only see the status if you have Team enabled too, since it's like a sub-component on the Team layout row
Who would benefit? Anyone trying to optimize their layouts What impact would it make? You wouldn't waste time trying to figure out why the status row wasn't showing up How should it work? It would either show you the status row even if you didn't ...
Allow user to select if they are rolling up to an initiative created within the workspace or an initiative created outside
When linking an epic or a feature to a initiative the search box appears retrives results for every product in the hieracy. This is a very important capability in Aha!, however the list can be hundreds of initiatives, and searching that list each ...
Andrew Brooks
almost 5 years ago
in Epics
0
Future consideration
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
over 6 years ago
in Epics
0
Unlikely to implement
Who would benefit? Product Managers What impact would it make? allow to comunicate a message for product initatves How should it work? be a template for description
Guest
over 1 year ago
in Epics
0
Future consideration
Epics as collections of Features (or Ideas) without being tied to a release.
We use Features as user stories that get individually worked within a release (development iteration). However, almost all of our Features roll up to Epics (which then roll up to Initiatives). The current format doesn't allow for the organization ...
Guest
over 3 years ago
in Epics
0
Future consideration
More flexibility in how lists of child items are displayed
Across Aha! one can see the child-items of a parent - for exaample, Master Features in an Initiative; or Features belonging to a Master Feature. These items are listed in a static fashion. The items are listed in an alphabetical order and may have...
Venky N
about 5 years ago
in Epics
1
Future consideration
Who would benefit? All Aha Users with configured workflows What impact would it make? Operational efficiency to avoid downloading a separate list to filter. How should it work? Bring in the available statuses from the workflow a filter options. Th...
Guest
over 1 year ago
in Epics
0
Future consideration