Epic
Sort by:
Recent
Status:
Future consideration
Showing 106
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
2
VOTE
6
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
If you link an initiative to an epic, it would be nice the features linked to the epic are automatically linked to the initiative
Who would benefit? Product owners What impact would it make? Less manual work How should it work? Link epic to an initiative Pop up to link the features as well (cfr when you move an epic to another release) Without use of automation rule (no ente...
0
Future consideration
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
4
VOTE
Prevent users from inadvertently moving Features' workspace
Who would benefit? Our company's 750+ workspaces What impact would it make? If not resolved, this can cause damage, manual work to re-create Aha! <> Jira integrations, and work becoming out of sync between the two. How should it work? We oft...
0
Future consideration
1
VOTE
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...
0
Future consideration
1
VOTE
make it easier to work with Epics
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 ...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved