Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Pinned ideas

PINNED Chrome extension to capture feedback from anywhere
What is the challenge? We work in many applications and Aha! can not build custom integrations for all of them. This makes it very hard to users of those applications to capture feedback and store it all in Aha! ideas. What is the impact? This res...

All ideas

Showing 9898

Be able to apply multiple sorting rules in a list report

What is the challenge? I would love to apply multiple sorting rules in a list report. (IE first sort by date, then by Status) What is the impact? Cleaner reporting to prioritize a list better Describe your idea I would love to apply multiple sorti...
Mary Daul about 1 year ago in Reports 0 Already exists

Update blank Jira fields on import to Aha! even if they are set up as a two-way sync

Currently only fields that are mapped one-way from Aha! to Jira will update when imported to Aha! - we import records from Jira to Aha! without a version set in Jira and Aha! automatically adds them to a default release in Aha! - we would like Aha...
Diane Metzger about 1 year ago in Integrations 0 Future consideration

Displaying requirements within the Retrospective report

Who would benefit? Our dev management team What impact would it make? Would provide much better insights into why a release went off track. Currently the "Records Added" section lists Epics & Features added after dev started. In our case, it's...
Sam Banks over 2 years ago in Releases 0 Future consideration

Azure DevOps integration support for designating default Iteration as backlog

Currently the Azure DevOps Services integration supports configuration of the project and the project area. All work items go to the root project iteration level. However, multiple teams may work in a single project and have a different iteration ...
Ronnie Merkel almost 6 years ago in Azure DevOps Services and Server 2 Future consideration

Add Visual Effort Indicator to Features on Starter Roadmap

Our business stakeholders, rightfully so, need to understand the level of effort involved in the various items on our roadmaps. At the most basic level, this equates to showing them the number of developers involved in a given item (epic/feature),...
Guest almost 6 years ago in Capacity planning / Roadmaps 0 Future consideration

Dependencies (adjustable) between different releases, if move the first release to another date, automatically move all depended releases

No description provided
Guest over 4 years ago in Dependencies / Releases 0 Will not implement

Decouple requirements from Features

Who would benefit? Users of AHA What impact would it make? Allow for my dynamics way of using AHA How should it work? One should be able to create a requirement (or whatever you want to name it) without being forced to link it to a feature. At Roc...
Guest over 2 years ago in Features 0 Unlikely to implement

Epic record link - search by ID

Currently, the user can link a feature to a master feature by searching by feature id. However, the user is unable to link a master deature by searching by master feature id. This creates an inconsistent user experience
Keith Davenport about 7 years ago in Epics 4 Future consideration

External facing product names

As a product manager I'd like to be able to define both an internal and an external product name. The case might be that our team and internal employees refer to a product as "X". Externally, our customers know the product as "Y" in marketing and ...
Scott Goldblatt over 9 years ago in Ideas 5 Already exists

Add more filters to integrations import

Who would benefit? aha admins What impact would it make? keeping Aha in sync with JIRA on the release. This would also help other internal stakeholders informed. How should it work? The integrations import desperately needs additional filtering cr...
Shri Iyer over 2 years ago in Jira 0 Already exists