Skip to Main Content
ADD A NEW IDEA

Integrations

Showing 916 of 8640

Integrate with Mural

Mural is a great visual management tool. Ideally Mural could be the foundation for the notes section in Aha!. Ideally....you could work on a Mural from within Aha!...so perhaps an integration of some sort. This allows for a virtual room where team...
Guest over 6 years ago in Integrations / Product 2 Unlikely to implement

Allow the JIRA integration to support mapping to more than one JIRA issue type and in Aha provide the ability to select the JIRA issue type to sync with

We use Aha for both Feature Requests and Defects and need to be able to designate if the JIRA issue type is an Epic, Story or Bug when linking to JIRA.
Kevin Konishi about 8 years ago in Jira 11 Already exists

Convert story to epic in Jira when promoting requirement to feature

In Aha! I have a feature with a set of requirements, all of which has been pushed to Jira as an epic with a set of stories. I want to convert one of the requirements to a new feature in Aha! and have the corresponding story in Jira changed to an e...
Guest almost 9 years ago in Jira 2 Future consideration

Integrate with http://phabricator.org

This is the open source ticketing tool that Facebook released.
Brian de Haaff over 9 years ago in Wanted 5 Unlikely to implement

Warn when there are incomplete Jira webhook settings

When setting up a webhook in Jira, you can choose specific events to trigger the webhook event. Some users accidentally select "Exclude body" which results in empty webhooks returning to Aha! and no updates being made. Other users create the webho...
Madeleine Black over 1 year ago in Jira 0 Future consideration

Make the standard tags field mappable for requirements

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 ...
Justin Waldorf almost 2 years ago in Integrations 1 Future consideration

Map to a persona name value in integrations

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
Barnett Klane over 4 years ago in Jira 3 Future consideration

When an integration update comes from JIRA, it would be useful to see the "integration" completed the update in history instead of the callback user.

The callback user usually is not the one making the update in JIRA. It is almost 100% someone else on the technology side and not the product team. JIRA indicates that the integration updated the JIRA issue. It would be nice if Aha did the same.
Wen-Wen Lin over 5 years ago in Jira 5 Future consideration

Include Area Path in VSTS Integration

I really like the VSTS integration 2.0, however could you add Area Path to the list of available fields that can be mapped to. This would be useful as in VSTS we use Area Path to note which dev team has picked up a feature and it would be great to...
Guest almost 6 years ago in Azure DevOps Services and Server 3 Future consideration

Integration with VersionOne

Bi-lateral sync with VersionOne
Guest over 7 years ago in Integrations 0 Unlikely to implement