Integrations

I'd like to export (or even better: sync) my Aha todos with Todoist via Zapier.com or Built.io. Zapier supports the webhook API, but To-dos are not listed a record type for which a callback can be done.

When comments are added to Aha from the Jira integration, they show up as having been created by Integration: Jira even though the comment includes the following: Created in Jira by Matthew Monahan (****@****.com) When I dig into the values in t...

When configuring a new Product in Aha to integrate with Jira: The backlogs are already in priority order in Jira. However, when syncing over to Aha!, the priority order does not carry over upon the first sync. I understand how to use the rank fiel...

What is the challenge? Could not use the new Jira object in the mappings What is the impact? Teams want to group similar Epics in capability. without this, we can group them for tracking Describe your idea We already have Aha Integration to Jira i...

We want to show a dependency of one of our Features on a deliverable from another team without having to create a separate feature and map and sync it through the regular JIRA integration. I think being able to import the JIRA link (and descriptio...

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

The "Update Records" feature currently updates all integrated records defined in the Azure DevOps integration. This could take quite some time if the number of records is high. Sometimes you only want to upgrade on a particular record type because...

When integrating AHA / Jira the field mapping only shows fields that can be editable. We are looking to bring in Created Date and Resolved Date on both the Jira epic and Jira story. These fields are dynamically created and populated based on the f...

Who would benefit? aha admins What impact would it make? keeping Aha in sync with JIRA on the release. This would also help other internal stakeholders informed. How should it work? The integrations import desperately needs additional filtering cr...

Currently, only the changes made to a JIRA issue are sent over to Aha! through the webhooks. We should have a way to force Aha! to synchronize all descriptions and fields from JIRA for an entire release.