Skip to Main Content
ADD A NEW IDEA

Epic

Showing 110

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

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 10 months 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 over 2 years ago in Epic 3 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 9 months ago in Epic 0 Future consideration

Automate feature creation on epics

Who would benefit? User teams that do a lot of repetitive work with contextual differences What impact would it make? It would help keep backlog items consistent and reduce the time needed for repetitive work created with necessary data relationsh...
David I. 7 months ago in Epic 0 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 about 3 years ago in Epic 1 Future consideration

Allow "Original Estimate and "Logged Effort" to be used in Calculated Columns

In Roadmaps list, having the ability to do calculated columns is incredibly powerful. However, we recently noticed that there are two fields we want to use to create charts that are not available to use. These are Original Estimate and Logged Effo...
Jared Gummig over 2 years ago in Epic 1 Future consideration

Allow conversion of Epic to Feature when the Epic contains features

When an Epic has no child features, you can convert it to a Feature. When an Epic has child features, today you cannot convert it to Feature. It would be a smoother workflow to allow Epics with child features to be converted to a Feature
Emily Yankush over 1 year ago in Epic 0 Future consideration

Make all standard fields available for automation

Automation Rules are incredibly powerful but are limited to a very small subset of standard fields per item (ideas, epics, features, initiatives, etc.). We're constantly finding ourselves wish that a standard field would exist so that we can creat...
Conner Helton 10 months ago in Epic 1 Future consideration

When adding features to an epic, I should be able to select multiple Features

When creating an epic, that has features that already exist. Its not possible to add more than one at one time. This means that each time I want to associate a feature, I have to open the select "Add" then the modal will appear to select existing ...
Andrew Brooks about 3 years ago in Epic 0 Future consideration