Epic
Sort by:
Trending
Status:
Future consideration
Showing 104
102
VOTE
6
VOTE
When we change Epics quarterly plan, user stories are being lost on the way
When we move Epic from one quarterly plan to another, if we drag them, it asks should the linked user stories be moved as well. However, if we simply change quarterly plan name in the field, user stories are not being moved. Same issue appears if ...
0
Future consideration
4
VOTE
Enable milestone key dates in epic & enable to be used in custom roadmap
Our team uses releases by a timeframe, not by an individual product release. Thus our release is made up of multiple epics that need a milestone per epic. Please enable a milestone option at the epic level in both the epic & custom roadmaps to...
0
Future consideration
8
VOTE
Automation Rules: Allow a Custom field of a related record to be updated to "MATCH"
We want to set an Automation Rule that will automatically set the value of a custom field at the feature level to "Match" the value in a custom field on the Epic. We also want the ability to make the value unchangeable on the feature - which we ca...
1
Future consideration
62
VOTE
Display and Report on Master Features and Features simultaneously
A number of our Product Managers had started using Master Features for their ability to combine Features that were more detailed than required for high level Roadmaps. However we quickly learned that viewing and reporting on Master Features and Fe...
10
Future consideration
49
VOTE
1
VOTE
Weigh epics based on story points for initiative progress
Not all of my epics under an initiative are equal size and Aha is considering them that way, which makes the progress inaccurate. For example, there are 5 epics under an initiative and Aha is treating them all as 20% of the Initiative. I want to t...
0
Future consideration
22
VOTE
Restrict the visibility of specific custom fields to different users
We use Aha! for all our product planning, however we currently do some financial estimates outside of Aha! which we don't want to share with the wider development team. This causes us to fragment our data and use permissions in other portals as th...
5
Future consideration
32
VOTE
Allow features to be shown (grouped) under the epic view within the Features Board.
By adding grouped features to the Master Feature view this would allow users to see which features are within their master features, and allow drag and drop of features between master features.
The display of features is currently not an optio...
3
Future consideration
5
VOTE
Allow conversion of Epic to Feature when the Epic contains features
When an Epic has no child features, you can convert it to a Feature. When an Epic has child features, today you cannot convert it to Feature. It would be a smoother workflow to allow Epics with child features to be converted to a Feature
0
Future consideration