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 6 years ago
in Epics
1
Already exists
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
about 3 years ago
in Epics
0
Future consideration
Limit Custom Fields Linked to Records Using Criteria
Ask : When creating a custom field related to a record (ex. Custom field showing all Epics from all other workspaces), I need a way to display only records that meet some criteria. Example of criteria would be: The records in a specific product li...
Mousa Mitwasi
almost 5 years 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
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
almost 7 years ago
in Epics
0
Unlikely to implement
Progress Bar- show color-coding from the Epic % complete
Who would benefit? Teams that work in Jira or teams that want to more easily see how Features are progressing What impact would it make? It gives more insight than just a Feature being done and the Epic progressing How should it work? Similar to h...
Jonathan bohaty
over 1 year ago
in Epics
0
Future consideration
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
almost 2 years 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
over 5 years ago
in Epics
1
Future consideration