Skip to Main Content

Share your product feedback

ADD A NEW IDEA

My votes: Epic

Showing 159 of 9055

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 11 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 over 3 years ago in Epic 2 Future consideration

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 ...
Guest 3 months ago in Epic 0 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 7 months ago in Epic 0 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 about 3 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 almost 2 years 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

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 4 months 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 over 1 year 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 over 3 years ago in Epic 0 Future consideration