All ideas

Unlike every other software, on the login screen Aha jumps a user "back" to the Aha logo when you hit Tab which returns you to the marketing site instead of advancing you to the Password field

I would like to be able to delete a contact from the list that i have not send the invite to. I created a standard list of contact and then confirmed with my sales team. In some cases they wanted to remove the contact from the list which i was una...

The default features workflow has three statuses: Not started In progress Done Done is currently defaulted to an organge colour. My expectation would be for Done to be a shade of light green indicating completion.

Features have a human readable "ticket number", which is <Project Name>-#, where # is incremented for each new one created. It would be helpful for Initiatives to as well, so that you can tell someone easily to go to an Initiative, you could...

We're using custom fields "Start Date" and "Planned Done Date" on our JIRA epics extensively, and we sync JIRA epics with Aha features. And we've added "Start Date" and "Planned Done Date" as custom fields in Aha features. When we use the Releases...

Under GitHub Commit Hook, when installing the Installation instructions in point 1 refer to Webhooks & Services_ section (see first image) In my Github its just Webhooks (see second image) Suggestion change text from Webhooks & Services_ t...

Rather than have a single set of defaults for a whole instance, allow a set of defaults from a given sub-hierarchy

There was a recent change to the formatting of the backlog releases v. actual releases on the epic/feature boards. This is creating bad formatting for those of us using dark readers to help with eyesight/migraines. Please update the formatting so ...

The current hierarchy is either too high, either too low for adequate product breakdown, and hence create difficulties in work assignment and follow up. Initiative to Epic=ok, Feature to Feature, ADD User Story level in between, Reqs to Reqs=ok

Integration developers need documentation for the fields in the notifications generated by a webhook event. There are multiple ID fields and other fields with similar names and non-intuitive functions. Developers are left to infer their purpose, a...