ADD A NEW IDEA

Epic

Showing 152

Copying an epic should also copy the associated Features.

Currently, if I want to copy a Master Feature, I must copy the Master Feature, then copy each associated Feature and map them to the Master Feature. This is time consuming and doesn't make a lot of sense.
doug evans over 5 years ago in Epic 8 Future consideration

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...
Guest about 1 month ago in Epic 0 Future consideration

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...
Mark Gerrard over 3 years ago in Epic 7 Future consideration

Inherited dependencies

What is the challenge? User have dependencies at Features, but if they Epic reports they will need to set up a new dependency to show in reports. What is the impact? Manual creation at the parent level, might be missed by the user. Describe your i...
Edgar Holguin 4 months ago in Epic 0 Future consideration

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...
Donald Hebert 8 months ago in Epic 0 Future consideration

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 ...
Guest about 1 year ago in Epic 0 Future consideration

"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...
Guest almost 3 years ago in Epic 3 Future consideration

Include Milestones in the expanded Release names section of the Epics Gantt Chart

Many companies use milestones to represent when a set of work items is to be delivered and these are only loosely coupled or decoupled from longer-term planning time boxes, which in Aha are best represented by Releases (e.g. quarterly time boxes)....
Rich Stewart over 3 years ago in Epic 2 Future consideration

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 ...
Tanya Lin 3 months ago in Epic 0 Future consideration

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...
Steven Schafer about 1 year ago in Epic 0 Future consideration