Who would benefit? PMs What impact would it make? Ability to more quickly prioritize, sequence and schedule work in the context of user need driven planning (epics) as opposed to functionality driven planning (features) How should it work? If you ...
Guest
over 1 year ago
in Epics
0
Future consideration
I manage a large portfolio for a product offering that is made up of several workspaces. I have an epic workflow board where i bring everyone together to get status and move epics across status columns in our workflow board. We recently went over ...
Lou Giambalvo
almost 4 years ago
in Epics
1
Future consideration
It would be helpful to be able to view 'Features' within an 'Epic' in the same way we view 'Requirements' within a 'Feature'; as list with similar functions such as reordering, expanding, etc.
Clare S
over 2 years ago
in Epics
0
Future consideration
API access for Master Feature->Features and vice versa dependencies
Our organization often maps Master Features against Features as dependencies, and there is presently no way to do analytics on this data because the information is not available via API. Please expose.
Frank Siler
over 5 years ago
in Epics
0
Future consideration
When we create an epic, and mark that its status is based on features, it should continue to adjust even if the origin feature reached 'ready to ship' and also the epic reached that state, if afterwards we are now adding new features with status u...
Ronit Binshtok
over 2 years ago
in Epics
0
Future consideration
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
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
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
over 4 years ago
in Epics
0
Future consideration
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
about 6 years ago
in Epics
3
Future consideration