Skip to Main Content

Share your product feedback

ADD A NEW IDEA

All ideas

Showing 5539

Make required fields consistent for virtual users

In the below screenshots, email address is a required field on the first screen, but not on the second. Email address shouldn't ever be required when creating a virtual user.
Bryan McElhinney about 3 years ago in Capacity planning 1 Future consideration

Keep notification's email subject consistent to allow email threads/conversations instead of single emails per change

As a user, I would have all the notifications email for specific ideas or releases in a single conversation/thread. In Gmail, if I receive multiple emails with the same subject, they get grouped in a conversation/thread. To do this, I believe the ...
Adrian Romero about 5 years ago in Comments / Notifications 0 Future consideration

Ability to filter out shipped epics

when doing things like assigning a feature to an epic, or viewing epics on any of the boards, it would be extremely useful to be able to filter out or separate out shipped epics (like is one with shipped releases)
Guest about 5 years ago in Features 0 Future consideration

Retain scorecard clickability in reports

We often send out reports with upcoming features or features/ideas that need to be prioritized where we include the Scorecard value. It would be helpful if the Scorecard field retained the ability to click on it to open the scorecard window to see...
Guest about 2 years ago in Reports 0 Future consideration

Enable ability to bulk edit scorecard parameters in the Aha scorecard via the list view

with hundreds of features, the ability to select and bulk edit one or more scorecard parameters is essential
Angela Brown about 5 years ago in Reports 1 Future consideration

Multiple Dependency Definitions appear in Gantt Chart Report

Today within the Gantt Chart view, the only Dependency Type that appears to be captured is "Dependent On" or "Dependency Of". This neglects other dependency types. All types should be included in this view
Josh Tambor about 5 years ago in Dependencies / Reports 0 Future consideration

If a new workflow is applied to a workspace, update any affected Automation rules

When you select a new status workflow for a workspace (any record type) it forces you to remap existing statuses to the new statuses. We should also update any automations to use the new statuses using the mapping the user selected when changing t...
Todd Meyer about 5 years ago in Application 0 Future consideration

Creating and Associating multiple epics with step in Features -> User Story Mapping

Who would benefit? Product planners What impact would it make? save so much time having to drag and drop and rearrange as you scale out/add detail to your user story maps How should it work? In user story mapping practice, you usually create the s...
Guest about 1 year ago in User story map 0 Future consideration

Ability to Configure Default View (Drawer / Details) for Records

Who would benefit? All Aha users What impact would it make? Provide consistent and optionable record viewing experience to users. How should it work? Provide the Drawer and Details view options in personal setting per user preference on viewing ...
Hank Liu about 1 year ago in Features 0 Future consideration

Automation Rule

1. Do we have option to set Automation Rule to convert idea to feature automatically based the status change? 2. Do we have option send promoted feature details to the original Idea submitter? 3. When feature is created status with in-design , it ...
Barathi S about 2 years ago in Application 1 Future consideration