Epic
Sort by:
Popular
Status:
Likely to implement
Showing 158
2
VOTE
Need specific support for user journeys
The customer success team suggested I just use initiatives for user journeys and master features for user journey steps, which is a good temporary fix. However, defining a user journey is a pretty specific thing that I think should be set apart fr...
2
Unlikely to implement
2
VOTE
Display master features for current product first
When applying a Master feature to a feature, you have to scroll through all the products' master features if your product is at the bottom of the list. It would be great if the Master Features for the Product you are currently navigating were at t...
0
Already exists
1
VOTE
Prevent epic and feature due dates being overwritten on creation by child records
Currently, if a user has set their epics or features to inherit dates from their children then when creating an epic or feature the due date is ignored and replaced with the date of the child records or is forced to be blank if no child records ex...
0
Future consideration
1
VOTE
Issue Count Limit for Unranked Epics (Prioritization View)
What is the challenge? We frequently run into issues with the epic prioritization view. On a workspace line level, we have more than 100 unranked epics across 3-4 workspaces. Whenever we run into this issue, the view does not even show the workspa...
0
Future consideration
1
VOTE
Allow epics to be created for workspace line level
What is the challenge? We have multiple product lines that include several product workspaces under them. We need to be able to create an aha epics for larger feature work at the product line level that spans multiple child product workspaces. Thi...
0
Future consideration
1
VOTE
Create a new record type called an "Enabler"
What is the challenge? We want to distinguish between Epics which end up in the product, and Enablers which are required to deliver the product but not a part of the product itself What is the impact? By not having a record type of Enabler, we can...
0
Unlikely to implement
1
VOTE
Release to be optional on Epics, or multi-select
What is the challenge? In the admin configuration for a workspace, Aha! provides a tooltip explanation for "Epics", which reads: "What are epics? Epics are used for bigger work items and can be used to group together many features, which can span ...
0
Future consideration
1
VOTE
Allow elements from a scorecard to be automatically populated in another scorecard
What is the challenge? I have two things that I need to be calculated using generally the same inputs. The calculations are completely different and we need to restrict what the person can enter and provide help text so we are using two separate s...
0
Future consideration
1
VOTE
Asking for more user-friendly IDs for custom table entries
What is the challenge? The current Custom table record IDs (e.g. 7576123412341234123) are long, complex, and difficult for users to remember and manage. What is the impact? Difficulty in communication and collaboration when users need to share or ...
0
Future consideration
1
VOTE
Automatically populate Epic end/due date only when last feature is completed, instead of continuously
What is the challenge? Epic due date is updated continuously when underlying features are completed/done if due date is set to "Calculate from features". What is the impact? Gives a "false positive" indication of an epic's due date which in turn i...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved