Integrations

When you add comments to a Feature, and you have integration with Azure DevOps (ADO) configured, you can have these comments passed back and forth. Unfortunately if you attach a file to a comment it will not get passed between Aha and ADO. When yo...

With the Jira integration it is possible to pull through the Sprint name as a custom field into Aha Master Features/Features. It would be useful to be pull through the sprint finish date and apply that to all linked items within Aha. This would al...

My team has switched from Fogbugz to Linear for ticket tracking. We'd like a two-way sync between Aha features and Linear Issues.

Currently we can rename the title of the Salesforce widget. We can also customize all the text within the Ideas portal in Aha. For us, we want to use this connection but we don't want to call them ideas, but rather e.g. Requirements. This is possi...

We are trying to close the feedback loop for our customers. As product ideas come in through ZenDesk, they are kicked to Aha! and then the product team updates each ticket with a status. That status, while reflected in the ZenDesk issue detail, do...

Both epics and features have the standard tags field mappable when setting up an integration. Requirements now have a standard tags field added to the record but it is not available in the mappings. It currently requires a custom field be created ...

It would be useful if we had the ability to push attachments made on comments, to Jira. Today, only direct attachments (to features or requirements) are supported, but from a UX perspective, attachment from comments should be included too, OR an a...

With Jira, a single Aha! webhook added at the system level supports updates across all Aha! integrations. This makes scaling integrations simple as after the first setup, a user never has to add another webhook. With Azure DevOps (TFS), each i...

What is the challenge? Currently, Aha integration with ADO syncs dependencies at Features level only. We need to also be able to sync the dependencies at Requirements/UserStories level.Including dependencies between Features and User Stories. What...

VSTS/TFS picklist custom fields are treated as strings and cannot support option mappings. Mapping a picklist field to an Aha! choice list field should provide the option to click Configure and map the choices.