ADD A NEW IDEA

Integrations

Showing 637

View in Aha! the author of a comment created in Azure DevOps

In integrations with Azure DevOps, comments created in ADO show the integration name rather than the individual as the creator of the comment when looking at it in Aha!. This can cause confusion for Aha! users who can't easily understand the conte...
Guest about 3 years ago in Integrations 1 Future consideration

JIRA integration needed at the portfolio and product family levels.

We use initiatives at all levels within Aha and need to be able to integrate those with JIRA for additional capacity reporting. If initiatives are available to be entered on those levels, it would be useful to have the integration setup available ...
Wen-Wen Lin almost 5 years ago in Jira 2 Future consideration

Link Salesforce opportunities to Features

Today, the SFDC integration can only link opportunities to ideas. It would be great to also link to features. This could help prioritize features that are still in a parking lot and would reduce the buden of merging ideas created via SFDC with exi...
Fabien Maisl almost 5 years ago in Salesforce 2 Future consideration

Allow for mapping to-dos in Asana integration

In some cases, Asana sub-tasks are more closely related to Aha! to-dos than requirements. For example, a feature may have to-dos related to marketing tasks which need to sync with Asana. An option to map To-dos to Tasks or Subtask would provide a ...
Austin Merritt almost 6 years ago in Asana / Integrations 4 Future consideration

Support bulk remove of JIRA links from "Features List"

Currently, JIRA links must be removed one at a time. On occasions, we'll find ourselves having to do larger bulk operations, and the manual removal of each link by clicking on the feature is time-consuming.
Guest almost 8 years ago in Jira 1 Future consideration

Support for Jira Code Markup

Need to support the Jira code markup option. If the developer enters sample code as part of the description in Jira, the description gets updated in Aha! However the code markup is translated into very large tables in Aha! At some point, Aha! u...
Guest about 8 years ago in Jira 2 Future consideration

Sync comments between aha features and pivotal tracker.

This would mean that our dev team and product managers can use a common discussion forum between the systems.
Guest about 9 years ago in Pivotal Tracker 1 Future consideration

DevOps Integration: Sync "Task" Workitems with Aha's "To-Dos"

Currently, our main work in DevOps gets done within Task items which also have effort spent inside. These however are not a sync-option within the "To-Do" level of Aha!. The fields "Name, Description, Assigned to, Due Date (and maybe effort or oth...
Michael Scholze over 3 years ago in Azure DevOps Services and Server 1 Future consideration

Sync releases for Azure DevOps integration

Currently we cannot push work back from Azure to Aha correctly as the releases/Iterations do not sync which causes manual work to move a card to the correct Aha release once imported. Iterations can be nested in ADO, and when you try to send recor...
Ronnie Merkel over 3 years ago in Azure DevOps Services and Server 0 Future consideration

Update records on all integrations linked to a template at one time

We anticipate having 150+ integrations based on a template (with the Rally integration). In order to add fields to the integrations, we edit the template and those updates/new fields flow to the individual integrations based on the template, howev...
Elaine Edwards over 4 years ago in Rally 1 Future consideration