Integrations may be common across products within the same product line. It would save time and the possibility to make setup mistakes if these integrations can be setup one level higher

Allow initiatives to sync to integrations as a first class object like features, requirements and releases. For the JIRA integration this would involve: 1. Allow the user to choose the JIRA issue type to sync initiatives with in the integration co...

When you initially import issues from Jira the Jira comments are not included. This means I have to copy them across manually for every issue - very time consuming. (Comments added to Jira subsequently do appear in Aha.) Please can you include Jir...

We recently made the update where we can populate a required custom field in Rally with a default value to facilitate the integration with required custom fields. This idea is to take it a step further and provide custom field integration mapping ...

Add an "Import from Rally" utility for importing existing features, user stories, etc. and supporting metadata into Aha! as Features and Requirements and creating corresponding links between the data objects in support of the bi-directional integr...

What is the challenge? When I run the Update records utility for many integrations, the background jobs page does not show an updated progress for each job. Also, if the job fails there is no link back to the integration so I can quickly find and ...

Currently the Aha! to Salesforce integration must be installed using the classic interface. After that, it can be used via the Lightning interface. As a Salesforce admin, it would be nice to be able to install the app via the Lightning interface a...

The current Aha! - GitHub integration lets you sync features to GitHub issues. This won't work in the opposite way. However, It'd be nice to have an editable field to reflect that the Aha! feature is linked to a GitHub issue.

We would like the ability to have new records created in JIRA/Rally automatically import into Aha! Currently, they have to be accepted in Aha! prior to import. This causes an extra step in our workflow we do not wish to have to go through each time.

When the Jira workflow is set up to "Close" a ticket with the resolution status of "won't fix," there currently is now way to map that against the Aha workflow. It would be great to also access the Resolution status from Jira to handle this case.