ADD A NEW IDEA

Integrations

Showing 947

Admin Summary Report for Integrations

Would it be possible, if at the end of the week, Aha! would send an email letting the admins know what occurred in their workspaces. For example, we would like to know if there were integration issues and any updates to fields on the Aha! or third...
Manny Pannu about 1 year ago in Integrations 0 Future consideration

Integration with Zoho Projects

Once the product roadmap is ready, it needs to be transferred to Zoho Project management platform (https://www.zoho.com/projects/) for product development.
Guest about 3 years ago in Integrations 0 Future consideration

JIRA Integration - Hide 'Send To' Options

Within the JIRA integration, add the ability to hide options to 'send to' JIRA and only show the 'link with existing' options. This would be helpful for integrations that are designed/configured to be only 1 way (JIRA to Aha).
Kyle Kinder about 1 year ago in Jira 1 Future consideration

Integrate Aha to-dos with Wunderlist

It would be great if you had an integration with Wunderlist, so that rather than my todos being siloed away in Aha from my other work todos, they were available in a specified, configured list in Wunderlist.
Guest over 7 years ago in Integrations / Wanted 1 Future consideration

Integration between Aha! and Jira Align (formerly Agilecraft)

Jira Align is a requirements tracking platform that was formerly Agilecraft, and is fully integrated with Jira. Our teams that are using both Jira and Jira Align are mapping their Epics in Jira to parent Epics in Jira Align, so that the roll-up pr...
Adam Zoghlin about 3 years ago in Integrations 1 Future consideration

Allow mapping Release as a field on Requirements in Azure DevOps integration

Due to our iterations setup in Azure DevOps (ADO) we do not currently map Releases as a record. We are sending this instead as a field on the Epic and Feature records to a custom field in ADO. We would like to do the same on Requirements but it is...
Guest about 3 years ago in Azure DevOps Services and Server 0 Future consideration

Ability to configure integrations not to create new records in Aha

In the 1.0 integrations I had configured it to not try to create new Aha! records when records were created in JIRA. I would like to be able to do the same in the 2.0 integrations. Currently when someone creates a new issue in JIRA I see this appe...
Kevin Burges over 6 years ago in Jira 0 Future consideration

Allow auto-import of JIRA issue without the need for a "parent record" (or just a pre-defined default like with manual import)

I was a bit confused when I could import items from JIRA manually, and webhooks were working both way, but when I made a new issue in JIRA, it was not getting auto-imported. I read through lots of really long explanations about the need for "paren...
Guest over 7 years ago in Jira 3 Unlikely to implement

Apply "Update records" to a subset of records in an integration

The "Update records" function is very useful when Aha! Roadmaps becomes out of sync with my development tool- I can use it to bulk-update all of my linked records to make sure they are up to date with Jira. But, there is risk inherent in this kind...
Reilly O'Connor about 2 years ago in Integrations 0 Future consideration

Limit workspace users choice to 1 user instead of multiple (like the Assigned to) field

I need to add the workspace users as a custom field in my template and currently it doesn't limit to just one user, it allows multiple users which I cannot have. Can we have an option to make it a single choice only. in the attached graphic is the...
Stacy Monnahan about 2 years ago in Azure DevOps Services and Server 0 Future consideration