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 9728 of 9728

Ability to switch to UK English - spelling

What is the challenge? Aha! is very American, but I'm not, and in a global role. Our company policy is to use UK English. What is the impact? All my content, looks like it is riddled with errors, as so much is underlined (as system is highlighting...
Guest over 1 year ago in Application 0 Future consideration

Ability to switch out of American - date format

What is the challenge? Aha! is very American, but myself and my team are global and from all over the world. What is the impact? Having American date entry formats has led to entry errors and confusion across people from different countries. Descr...
Guest over 1 year ago in Application 0 Future consideration

"Created" and "Last Updated" dates for Product/Files

Please add system metadata items (dates) "created" and "last updated" for each "Product/File" please.
Guest over 9 years ago in Application 1 Will not implement

"Created" and "Last Updated" dates for Product/Notes

Please add system metadata items (dates) "created" and "last updated" for each "Product/Note" please.
Guest over 9 years ago in Notes 0 Will not implement

Add ability to transfer requirements between features and features between master features (epics)

If you take the typical hierarchy VSTS, of Epics, Features and Product Backlog items, its is great that with Integrations 2.0 we can map these to Master Features (we call these Epics), Features and Requirements (we call this PBI's). However we are...
Richard Harrison over 7 years ago in Azure DevOps Services and Server 0 Future consideration

Map a sub-release to more than 1 master release?

This feature doesn't appear to be supported, but I want to ask anyways. I am looking to map a sub-release to more than (1) master release. The master release roadmap view is highly valuable to me for communicating "market" releases across all prod...
Suzanne Vaughan almost 11 years ago in  4 Unlikely to implement

Ability to include multiple record types within the cells of the pivot report

In order to have a pivot report for long term roadmap that its columns are timeframes (e.g. FY23 Q3, FY23 Q4, FY24 H1, FY24 H2, FY25) rows are workplaces for example (or any other custom field for describing the domain) cells are records that can ...
Ronit Binshtok about 3 years ago in Reports 0 Future consideration

Custom calendar resolutions to include timeframe in roadmap reports

Today the calendar resolution in roadmap reports, can be set to auto fit, quarters, months, weeks or days. It is essential having an option to set the resolution according to timeframe field, this will allow to change the scale and adjust it to th...
Ronit Binshtok about 3 years ago in Roadmaps 0 Future consideration

Goal with status category "Will not do" should not appear as a selectable Goal for any record

When a Goal is "abandoned", the out-of-box Goal workflow has a status for that, using the "Will not do" status category. The benefit of this behavior is that the history is viewable and reportable. However, a Goal with a status category "Will not ...
Guest about 6 years ago in Strategy 0 Unlikely to implement

Enhancement to custom fields for ADO integration

What is the challenge? Manual processes required What is the impact? Improve ability for automation Describe your idea "I have an ADO integration set up (one way) to allow me to raise requests to a team direct from Aha. However, they require a spe...
Ben Bulow over 1 year ago in Integrations 0 Future consideration