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 Epic
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
about 5 years ago
in Epic
0
Future consideration
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 Epic
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
over 6 years ago
in Epic
0
Unlikely to implement
Report to show how many work requests are linked to each epic
Ability to produce report showing how many Work Requests are linked to each Epic. As well as to show hierarchical linkage: Initiative - Epic/s - Work Requests against each Epic
Guest
over 1 year ago
in Epic
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
almost 3 years ago
in Epic
0
Future consideration
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
over 5 years ago
in Epic
1
Already exists
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 Epic
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
almost 6 years ago
in Epic
3
Future consideration