Currently only Aha! Users and Reviewers can add Ideas via Slack integration. Non-Users/Reviewers have always been able to submit ideas via the web portal so extending that as part of Slack -> Aha! seems like a next step. Our users would like t...

What is the challenge? The list of to-dos on my notes/documents can get long. The ability to filter to-dos based on a particular field would be helpful. Also the ability to expose a field, such as tags, on the to-do list (without clicking into t...

What is the challenge? Currently, when searching in the Knowledge Base, only the current page is shown, along with Previous and Next buttons. Users have no visibility into how many total result pages exist. This created several challenges: U...

What is the challenge? When "Use Jira and overwrite Aha!" is selected, there is a full sync of all fields, allowing fields to update in Jira. But, when "Use Aha! and overwrite Jira" is selected, that same full sync is not performed, and one-way ...

What is the challenge? We need a more flexible Kanban workflow view which is based on sprints (custom field) Currently it is only possible to have a Kanban view with status for the features. We need a way to display what is planned in every spri...

What is the challenge? Currently we'll have to change the links on the home page and create or manually redirect new links for our product/support teams to share release notes documents. This is especially problematic for teams that release freque...

Who would benefit? Customer using Jira epics to manage work in multiple projects What impact would it make? They would be able to see their progress in Aha! correctly How should it work? If you have an epic in Project A, and it has multiple childr...

Add the ability to map custom fields from custom tables in Aha! to Jira.

I'd like to be able to create a non-production sandbox environment for my Aha! account so I can test account level settings and configurations, like SSO, without impacting my real settings and workspaces. A separate account is not ideal as I'd lik...

For large product teams there will be multiple initiatives and associated estimates. It would be beneficial to be able to import estimates when an annual planning process is underway, to reduce manual workload and assist in assuring quality.