ADD A NEW IDEA

Integrations

Showing 945

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

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

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

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

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 Future consideration

Azure DevOps integration support for designating default Iteration as backlog

Currently the Azure DevOps Services integration supports configuration of the project and the project area. All work items go to the root project iteration level. However, multiple teams may work in a single project and have a different iteration ...
Ronnie Merkel over 4 years ago in Azure DevOps Services and Server 2 Future consideration

Create Feature Delivery Type field to map to Rally Feature

This field is required in Rally as it is used for Fixed Capacity Billing.
Guest over 4 years ago in Rally 0 Future consideration

Update mapped initiative field in integration when changing text of initiative name

The initiative field is available in the Jira integration under the Aha! feature record. It works as expected when initially sending the Aha! feature to Jira. (Note: this is not the use case of mapping the initiative record.) However, the mapped i...
Craig Pflumm over 4 years ago in Integrations 0 Future consideration

better redmine integration - requirements are children of features, and tasks are children of requirements

redmine integration is very helpful and needed. "When a feature is copied to Redmine one issue will be created for the feature. If the feature has requirements then each requirement will also be sent as an issue." there should be a way of re...
Michael Martini almost 9 years ago in Integrations 0 Unlikely to implement