Issue with list field mapping with integrations 2.0 when your list of available values is long. If you have a custom list field with lots of values (20+) and a corresponding long list field in Jira. To map the values between the two systems is ver...

Right now if I integrate with Box, link a file and then try to open the file..I am presented with a preview or download option. Why can't I open it for editing like I can straight out of the Box desktop App? I want to be in Aha!...have a file link...

Microsoft flow has over 175 triggers currently available. Examples include Zendesk - When an Item is created, Wunderlist - When a New task is created, Saleforce - When a record is created, Pivotal Tracker - When a story is created, etc. Having acc...

I can create a relationship for Releases at the requirement level even though requirements do not inherently have a release field, this appears to be derived from the feature. I should also be able to create a relationship to the Master Feature in...

I'd like to see the Aha!/JIRA integration be updated to have an option to set dates of features (and possibly other items) based on Status that is in JIRA. Example: I create a Feature in Aha! and integrate/export to JIRA When Feature (referred t...

Integrations 2.0 - Please only show valid integration directions for Release <-> Fix Version. I had opened ticket https://support.aha.io/hc/requests/176083 because I could not connect to the Jira version using Actions > "Link with existin...

In integrations 1.0 if I mapped Features = Story Requirement = Task Aha! would send the records to JIRA and create a "Relates to" dependency between the Story and the Task to visualize in JIRA that the two records should be related to each other. ...

Currently, the 2.0 integration does not support sending the Aha! rank to Rally in the same manner as the 1.0 integration - it cannot actually affect the ranking of items in Rally. As a customer who was using this in 1.0, we would like it to be ava...

In 1.0, when using a template, you could choose what fields/behaviors to inherit from the template, and which to customize for that particular integration. This was useful for custom fields (now using a constant in 2.0) which will change from prod...

Currently, when a mockup is updated or deleted, the file does not stay in sync with an integrated system. Ideally, the same mockup file would continue to get updated across the systems.