Presently, there isn't a way to have requirements in a draft status like there are with features. This tends to be somewhat problematic when you have multiple requirements types you work with e.g. subtasks and user stories. It will automatically s...

We want to automate responses that come in from our NPS(Qualtrics) to flow into the VoC Ideas Portal (Aha).

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 ...

Is it possible to have a custom field visible on the zendesk create idea/link form? We are starting to using a custom tag field to help identify product components. It would greatly help if we could apply categories and custom field information wh...

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...

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...

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

Currently, users of the Salesforce <> Aha! integration can create / link 'Aha! Ideas' to 'Salesforce Opportunities'. Further those 'Aha! ideas' can be promoted to / linked with 'Aha! Features'. As a user of the Salesforce <> Aha! inte...

When you add comments to a Feature, and you have integration with Azure DevOps (ADO) configured, you can have these comments passed back and forth. Unfortunately if you attach a file to a comment it will not get passed between Aha and ADO. When yo...

What is the challenge? Our organization has strict reporting coming out of Aha! that requires records to only be connected with 1 record in downstream systems (Jira in our case). Aha! currently allows you to intentionally link multiple Aha! record...