What is the challenge? As we do not use releases for some workspaces not everything pulls in automatically, so there are things in the integration updates tab that we don't know are there until we check it. What is the impact? Sometimes we...

What is the challenge? Currently there are a few user fields from ADO server accounts available to map to Aha!'s Created by User, but the Created By user is not displaying as an option. What is the impact? Users are unable to map the created by fi...

If you have an integration template with mappings that are inherited by child integrations, you can adjust the mapping step on that integration template to propagate your new mapping to all the integrations using that template. If you are doing so...

These are critical to the success of our organization wide integration efforts which are ramping up very soon. Set a resolution in Jira when record is closed in Aha When Jira issues are closed the user is required to set a resolution during the tr...

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.

We anticipate having 150+ integrations based on a template (with the Rally integration). In order to add fields to the integrations, we edit the template and those updates/new fields flow to the individual integrations based on the template, howev...

Right now we leverage personas to describe who a release is targeting, where we'd love to be able to push the text value into our JIRA mapping

Currently we cannot push work back from Azure to Aha correctly as the releases/Iterations do not sync which causes manual work to move a card to the correct Aha release once imported. Iterations can be nested in ADO, and when you try to send recor...

Who would benefit? Users of both Aha and those who are not direct users of Aha on a daily basis but who relay on outputs from the platform. What impact would it have? It would simply data sharing and through Microsoft products such as Teams, Word,...

We are trying sync the Feature order from Aha to VSTS (never the other way around). Keeping the Features in VSTS in the same order in Aha is in our use case, critical to using the integration. The reason that it fails is because matching the Aha R...