ADD A NEW IDEA

Integrations

Showing 923 of 8737

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 over 2 years ago in Asana 0 Future consideration

Including Attachments from Comments for Jira Integration

It would be useful if we had the ability to push attachments made on comments, to Jira. Today, only direct attachments (to features or requirements) are supported, but from a UX perspective, attachment from comments should be included too, OR an a...
Reut Levi about 4 years ago in Integrations 3 Future consideration

Support the ability to change a Jira project key

Aha! needs the ability to support changing a Jira project key. Occasionally teams change their focus and the Jira project name and key need to be changed to reflect that so Aha! needs to be able to support that as well.
Wayland Fox over 3 years ago in Jira 0 Future consideration

Allow mapping to the Rally iteration field

There is a built-in Rally field named iteration. It would be useful in many situations to map the iteration field to an Aha! field.
Austin Merritt about 2 years ago in Rally 3 Future consideration

Ability to Integrate Ideas with Jira Service Desk

What is the challenge? I am using a Jira Service Desk to capture new product and project requests and would like to use the Aha! Ideas for review and prioritization before sending to a specific Aha! Product Workspace. What is the impact? Today I h...
Matt L 2 months ago in Jira 0 Future consideration

Dovetail integration

Would love to see a dovetail integration so we can map UXR into our Aha Initiative, Epics, etc.
Guest 12 months ago in Wanted 0 Future consideration

Clubhouse integration

Clubhouse is gaining a full head of steam and being adopted widely as a replacement for Trello and Jira - it strikes a great balance between the two. We're currently evaluating a move from PivotalTracker to Clubhouse, and while we're excited by th...
Guest over 6 years ago in Wanted 9 Future consideration

Map VSTS/TFS picklist custom fields to Aha! choice list fields

VSTS/TFS picklist custom fields are treated as strings and cannot support option mappings. Mapping a picklist field to an Aha! choice list field should provide the option to click Configure and map the choices.
Tessa Adair over 5 years ago in Azure DevOps Services and Server 9 Future consideration

Allow a single Azure DevOps webhook to support updates across multiple Aha! integrations

With Jira, a single Aha! webhook added at the system level supports updates across all Aha! integrations. This makes scaling integrations simple as after the first setup, a user never has to add another webhook. With Azure DevOps (TFS), ea...
Guest almost 5 years ago in Azure DevOps Services and Server 1 Future consideration

Mark linked Jira tickets that have been deleted in Aha

I noticed that when deleting a feature in Aha! that is linked to Jira, Aha! doesn't delete the linked ticket. I disagree with your design decision, but the message from support makes it clear that you're firm in that direction. Still, when an Aha!...
Guest about 7 years ago in Integrations 4 Planning to implement