Epics
Sort by:
Trending
Status:
Showing 172
1
VOTE
Realistic View of Annual Planning Roadmap
What is the challenge? When we do annual planning, we do it in the form of EPICs. We typically arrange these into one or more planning releases (e.g., 2025, Q1 2025, 2H 2025, etc.). At this stage few have features under them, which is fine. As we ...
0
Future consideration
3
VOTE
Propagate Epic status change to linked Features
What is the challenge? Change in Epic status not reflected in associated Features What is the impact? Lack of status sync between Epic & Features Describe your idea We leverage Epic as the primary record for approval workflow. I would like to ...
0
Already exists
58
VOTE
9
VOTE
Display capacity line on Releases when looking at Epics board view
What is the challenge? When viewing the Epics on a board view, a capacity line does not appear even when "Epics" or "Features and epics" are used for the calculation. What is the impact? When estimation is done at the epic level, and epics are use...
0
Future consideration
6
VOTE
Ensure features and epics roll up to an objective/initiative pair
What is the challenge? We've defined a set of objectives (goals) and a set of initiatives under each goal. But the UI allows epic and feature creators to select objectives and initiatives that are independent of one another. What is the impact? Th...
0
Future consideration
35
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...
8
Future consideration
4
VOTE
Rearrange the order of Features in an Epic
What is the challenge? In the Epic detail view, I see all the related Features. I am not able to rearrange the order of these. (However, I AM able to rearrange the order of Requirements on a Feature). What is the impact? I don't have a way of sett...
0
Future consideration
3
VOTE
8
VOTE
Ability to Configure Epic View as Default for all workspace views (Board / Prioritization)
Who would benefit? Enterprises who maintain Epic only or use Epic as primary record type. What impact would it make? Reduce confusion. The teams are currently directed to feature view on the board and prioritization view by default. Per Aha concie...
0
Future consideration
1
VOTE
Reload Configuration in an Integration Template using bulk edit via List
What is the challenge? When using an integration template to Jira in multiple workspaces and there is a change (e.g. adding a new field, remove fields, etc.) the propagation of the change does not happen automatically What is the impact? Time cons...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved