Epic
Sort by:
Trending
Status:
Showing 157
57
VOTE
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
33
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...
7
Future consideration
2
VOTE
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
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
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
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
14
VOTE
"related" features/activities have details
In my Aha boards, I have epics/projects that have "related" features/activities. One thing I have found is that it can be difficult to see details for the lower level features/activities without going into the ticket itself. Under activities in th...
3
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved