Skip to Main Content
ADD A NEW IDEA

Integrations

Showing 871

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 1 year ago in Integrations 1 Future consideration

Integration with MS project

It would be great to tie into MS project for the high level milestones and phases so as either is updated....it would update the connection.
Guest almost 7 years ago in Wanted 10 Future consideration

DevOps Integration -- Support rendering of images embedded in description field

Currently when you import from Azure DevOps, if you have images embedded into the description field, they come over as a link in the Aha! description field, e.g. imagename.png. It would be great if they would render in Aha! like they do in DevOps....
Mike Maylone over 3 years ago in Azure DevOps Services and Server 9 Future consideration

"Real" 2-way integration with pivotal

The pivotal integration only allows for 2-way integration only if originally pushed from aha initially. Even then it's pretty limited to status and description. If I create an 'feature' in aha which maps to an 'epic' in pivotal, and someone add...
Guest about 9 years ago in Pivotal Tracker 23 Future consideration

Ability to map JIRA Team-field to a custom field in AHA

In integration 1,0 it was possible to map JIRA team field to a customfield in AHA, but in the new 2.0 integration that is't possible
Guest almost 6 years ago in Jira 10 Future consideration

Configurable destination of imported features

As a product manager, I should have control over the destination of where imported features and epics go so that they are in the release or parking lot where they belong. Today, the destination of imported items seems almost up to chance although ...
Tom Beck almost 6 years ago in Azure DevOps Services and Server 9 Future consideration

Allow attachments to Feature comments to be integrated to Azure DevOps

When you add comments to a Feature, and you have integration with Azure DevOps (ADO) configured, you can have these comments passed back and forth. Unfortunately if you attach a file to a comment it will not get passed between Aha and ADO. When yo...
Guest over 3 years ago in Azure DevOps Services and Server 0 Future consideration

Customize fields in the Slack integration

Who would benefit? Internal stakeholders giving feedback to product teams What impact would it make? Reduce overhead in editing ideas once they have been pushed to Aha through the Slack integration How should it work? When creating an idea using t...
Guest about 1 month ago in Slack 0 Likely to implement

Integrate with Invision

I’m not sure if Invision supports an API yet, but it would be an ideal integration for Aha. Right now, I think Aha does a great job of what I would call the front end of the funnel for product management: capturing ideas, managing a backlog, high ...
Chris Waters about 9 years ago in Wanted 18 Future consideration

Add 2-way integration mapping for release start and end dates

Release start date can currently only be mapped 1-way from Aha! to Jira (or any development system.) This is because that date used to be calculated based on features and phases in the release. Now that this date is set manually, it should be poss...
Austin Merritt almost 4 years ago in Azure DevOps Services and Server  / Integrations / Jira / Rally 1 Future consideration