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

Show required fields in integration mapping

When setting up an integration, it would be helpful to have a way to be prompted to map required fields in Jira. Currently, it is possible to create an integration that does not have field mappings for required fields in Jira. This causes the inte...
Madeleine Black over 3 years ago in Jira 1 Future consideration

Do not allow requirements to be mapped without a Links To relationship set

It is possible to create an integration where you have requirements mapped to a Jira record type, and where you have no Links To relationship established to a parent record in Aha! This results in import errors where requirements cannot be importe...
Madeleine Black over 3 years ago in Jira 0 Future consideration

Send report notification ONLY if there is data in the report

If a report returns no data then the notification shouldn't be sent via email. It should only send the notification if there is at least one row of data.
Guest almost 3 years ago in Reports 0 Future consideration

Customizable Terminology for Proxy Vote

The term "proxy vote" is not intuitive, which I believe is the reason some folks end up not using it. I would like to change it for "Voting on behalf of a client".
Guest about 5 years ago in Voting 4 Future consideration

Add a GANTT customize view - "hide phases" option

The GANTT chart is currently the only roadmap-like display that is capable of displaying the rollup release properly. In high-level reviews with executives, when focused on features, the GANTT delivers exactly what is needed, BUT the phases can be...
Guest about 4 years ago in Releases 0 Already exists

Bigger Input boxes on Prioritization feature

The input text boxes should be bigger. We can't see the whole number. There is plenty of room to make them bigger.
Guest over 3 years ago in Features 0 Future consideration

to-dos in a release template should inherit the phase or milestone dates

The release template concept is great, but the ability to assign tasks to these things is what helps get the work actually done. You can put a to-do into the release template, but when a release is instantiated on that template, all the to-dos hav...
Guest over 8 years ago in Releases 4 Future consideration

Include newly created epics and features (and allow filtering) on starter roadmap

One item I hate to do is go back an update reports every week with tedious manual steps. Roadmaps are nice but have two big problems for me: When the design team adds new Epics/Features I need to go manually add them to the selected things to incl...
Guest about 5 years ago in Roadmaps 5 Future consideration

New User Story Map entered Epics should still require required fields and load the standard description field template

Problem: When adding entities (e.g., Epics) via the User Story Map, the user is not prompted to enter in required fields and the predefined Epic template is not loaded in the description field. This bypasses the Epic creation protocols elsewhere i...
Guest about 4 years ago in User story map 0 Future consideration

Configure AHA! to support GSuite - sheets, slides, docs, etc.

We are a company that uses GSuite, this would allow us to pull data into our collaborative space and manipulate reports to personalize further than what AHA! current allows. Currently the inability to use AHA with GSuite causes delays and setbacks...
Guest over 5 years ago in Integrations 0 Future consideration