Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 950 of 9166

Allow use of Mapped fields template with one field difference for each integration

What is the challenge? Can't use Mapping Integration template. Have to update multiple integration for every mapping change since one has to be different. What is the impact? Would save a ton of time for our team. Describe your idea We have around...
Alex Berestenko 2 months ago in Azure DevOps Services and Server 0 Future consideration

Manual Sending of Requirements to integrated development tool

Presently, there isn't a way to have requirements in a draft status like there are with features. This tends to be somewhat problematic when you have multiple requirements types you work with e.g. subtasks and user stories. It will automatically s...
I R almost 2 years ago in Jira 2 Future consideration

Integration with Intercom

link/create conversation to idea
Guest about 10 years ago in Ideas / Integrations 24 Future consideration

MS Viva Goals integration

Who would benefit? Companies that leverage Viva Goals for OKR & initiative tracking in addition to Aha! Roadmaps What impact would it make? This would allow Product Managers and similar personas to continue the deep product-focused efforts in ...
David I. 12 months ago in Integrations 2 Future consideration

The ability to use an integration as a template prior to it's first time being enabled

What is the challenge? It's currently possible to use a disabled integration as a template, but before that is possible, you must first enable the integration and then disable it. What is the impact? This forces an extra step as users may want to ...
Stephanie Lechner 4 months ago in Integrations 0 Future consideration

Update blank Jira fields on import to Aha! even if they are set up as a two-way sync

Currently only fields that are mapped one-way from Aha! to Jira will update when imported to Aha! - we import records from Jira to Aha! without a version set in Jira and Aha! automatically adds them to a default release in Aha! - we would like Aha...
Diane Metzger about 1 month ago in Integrations 0 Future consideration

Record successful updates in Aha! from Jira "update records" action

What is the challenge? Currently, there are log events for successful updates made from Jira when using the "Update Records" action What is the impact? Users have no way of knowing which records were successfully updated and what fields were chang...
Stephanie Lechner 7 months 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 over 2 years ago in Integrations 3 Future consideration

Integration with Pendo

Pendo is a great tool that our company uses to see how our clients interact with our product. I'd love to be able to pull in some of the analytics of product use into Aha. For example, how many users are using this new feature we launched, etc.
Guest about 6 years ago in Integrations 2 Unlikely to implement

Integration 2.0 for Gitlab

Gitlab is an important integration, but still not covered by the new 2.0 integrations
Fabio Brito over 5 years ago in Integrations 8 Future consideration