Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 965 of 9351

Ability to create a report of integration errors across multiple workspaces

Currently the only way to look at the integration errors across multiple workspaces is to bring up the Integration Updates dialog and use the Send outgoing changes tab. But you can't filter on error text, or expand the window to see the everything...
Jor Bratko almost 4 years ago in Jira 6 Likely to implement

Product Line initiatives linked back to Jira Epic

We have the following workspace hierarchy; Product Line A Product B Product C Each Product is setup to integrate with a different Jira Project. If I create a feature in Product C and link it to an initiative in Product Line A, the following happen...
Bill Simakis about 5 years ago in Jira 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 6 years ago in Jira 2 Future consideration

Lock down integration templates

We have almost 200 integrations based on 1 template, and users are going in and mistakenly modifying the template which is locking other users out. We would like to only Admins to be able to change the template, including the Based on Template ch...
Guest almost 6 years ago in Integrations 1 Unlikely to implement

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 6 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 7 years ago in Asana / Integrations 4 Future consideration

Develop Aha! triggers for Microsoft flow

Microsoft flow has over 175 triggers currently available. Examples include Zendesk - When an Item is created, Wunderlist - When a New task is created, Saleforce - When a record is created, Pivotal Tracker - When a story is created, etc. Having acc...
Guest over 7 years ago in Integrations 0 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! upda...
Guest about 9 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 10 years ago in Pivotal Tracker 1 Will not implement

Allow record mapping to Asana Projects

Asana best practices recommend projects represent distinct bodies of work with start and end dates. The Aha! integration requires, in the set up, selection of an Asana Project to connect the workspace to. This requires a new integration for every ...
Bonnie Trei about 3 years ago in Asana 0 Future consideration