Would be great to export/import the requirements to POLARION so we have a smooth transistion in between the product management and R&D. Any chance? https://polarion.plm.automation.siemens.com/?gclid=EAIaIQobChMIg63ug-DN2QIVq7_tCh1gIAHfEAAY...

For users sending an idea or feature to Aha! from Slack it would be helpful to be able to optionally include a description from Slack instead of having to open Aha! to add it. The button link that opens the idea or feature is nice, but the ability...

For Epics which get initiated in Aha and flow down to JIRA, we want to enable 2-way integration so that updates which happen in JIRA are realized in Aha. However, if a NEW Epic is initiated on the JIRA side, we may not want that to be visible in A...

Integration With Leankit as With JIRA would help in Our effectivness and use of Aha as a portfolio system.

Right now we have a TFS integration configured with Aha which requires us to use an AD service account for TFS. This service account password needs to be manually added within Aha! however we have a policy that all our service accounts require pas...

When using the requirements level estimates to drive the total estimate on the feature level we would like the feature level estimate to be reduced when a requirement is marked in a complete status. Also we would like to have the feature status au...

I'd like to be able to see the changes in each item directly in the integration updates main window, without having to click into each item individually. Perhaps, allow adding what fields you want to see in that main window.

It makes no sense that this isn't available today. All other idea submissions generate such notifications on status changes. This at least should be an option I can turn on when setting up the integration.

It would be helpful if Requirements were built out so that they can be imported from jira 2.0 AND moved from feature to feature as easily and features are moved betweeen master features.

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