Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Epics

Aha! to preserve Jira/Atlassian Status monikers on sync

What is the challenge? In Jira/Atlassian, you have the option of adding in status "cards" for colorful "On Track", "At Risk" type status'. Some of our team members do this in Jira, but when it syncs with Aha! this is lost and removed. What is the...
Jeff Broderick 2 months ago in Epics Future consideration

Track when artifacts are created with AI and be able to report on the field

What is the challenge? What is the impact? Describe your idea
Julie Klovstad about 1 year ago in Epics Future consideration

Visualize Epics on a timeline in Aha! Teamwork

What is the challenge? While you can create Epics within Aha! Teamwork, there is no way to visualise them on a timeline. Currently: • Epics do not appear in the Timeline view. • There is no alternative Gantt or custom timeline view in Teamwork...
Justin Woods 7 months ago in Epics Future consideration

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...
Maria Plotkina about 2 years ago in Epics Future consideration

Remove irrelevant goals and initiatives when adding them to epics or features

What is the challenge? When adding an initiative or a goal to an epic or feature I'm presented with a list which includes items from other workspaces and/or items which are already achieved What is the impact? This makes it harder to find a releva...
John P over 1 year ago in Epics Future consideration

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...
Hank Liu about 2 years ago in Epics Future consideration

Allow new conditions in Delivery Risks

What is the challenge? Delivery risks are a great way to keep track of work that is at risk for a variety of reasons. Our challenge is we use various custom fields What is the impact? We don´t have a way to validate custom fields are filled or com...
Edgar Holguin about 1 year ago in Epics Future consideration

Rename "Aha! score" to "product value" during mapping

What is the challenge? Using ADO for product engineering, wanted to map "product value" to ADO. Didn't find it in the mappings field. Because it was listed as "Aha! score". Could confirm it by testing. We are using default terminology. What ...
Guest 3 months ago in Epics Future consideration

Ensure features and epics roll up to an objective/initiative pair

What is the challenge? We've defined a set of objectives (goals) and a set of initiatives under each goal. But the UI allows epic and feature creators to select objectives and initiatives that are independent of one another. What is the impact? Th...
Sandy Kobayashi over 1 year ago in Epics Future consideration

Automatically set same custom predefined tag from Epic on Feature when created from Epic

What is the challenge? When creating a Feature from an Epic, add the same custom predefined tags from that Epic to the new Feature. What is the impact? No custom predefined tags needs to be manually applied on the Feature after it is creat...
Guest 6 months ago in Epics Future consideration