Currently, enhancements are all listed together. Hidden in the text, you can usually find an "Availble with Enterprise+" or similar. But it's time consuming, and annoying to read about an enhancement, and then find out it's not relevant to your pa...

Currently, when you send an Epic to Jira, all of its features are sent, but they are sent as the default Feature type instead of the types that they were actually categorized. Often the product person is working in Aha! and doesn't want to yet sen...

Hello, since JIRA is emptying the value of active sprint, but not emitting this information via webhook, aha retains last active sprint in active sprint field. Which is cool as this actually enables creating a pivot report that would show backlog ...

Integrate with SpiraTeam (ALM from Inflectra)

When a file has been uploaded to aha that is larger than the maximum file size,then integrate without the file in TFS, adding a note indicating this. This will allow the team to collborate on the TFS items without having to delete the file.

My idea form allows users to submit ideas anonymously, and then it notifies our user community slack channel. This prompts great discussion and votes on good ideas. My problem is that even though someone submits the idea anonymously, the user’s em...

The current UI for selecting a product when raising a new idea in Salesforce doesn't look great and isn't particularly inviting for new users to interact with. Perhaps something more central with our portal logo above. Even better - make this some...

My organization uses Jira to track development work. We create Roadmaps for leadership to track progress. Jira Epics and linked to the Aha! Epics on said Roadmaps. Occasionally we will have one Jira Epic that will relate to multiple Aha! Epics in ...

It is not currently possible to map to Rally calculated fields in the integration with Aha! Roadmaps, but it would be useful to be able to do so (for example, to map to a field that calculates).

Please add a "Two way integration" (set once) feature in Integrations 2.0. Use case: the Feature Name (in Aha) and its corresponding Summary (in Jira) are not always the same. For example, the name in Aha is usually short so it shows well on the r...