ADD A NEW IDEA

My ideas: Integrations

Showing 932

Add ability to map Custom Aha! Tables to Jira

Add the ability to map custom fields from custom tables in Aha! to Jira.
Guest about 7 years ago in Jira 5 Future consideration

Integrations 2.0: Add dependency link to connect records without natural relationships together

In integrations 1.0 if I mappedFeatures = StoryRequirement = TaskAha! would send the records to JIRA and create a "Relates to" dependency between the Story and the Task to visualize in JIRA that the two records should be related to each other.In 2...
Danny Archer over 6 years ago in Jira 3 Future consideration

Add support to map Azure Boolean Fields to Aha

This request is to support the mapping of ADO boolean fields to Aha predefined droplist and tag fields. Currently, Azure DevOps Boolean fields (true/false) cannot be mapped to Aha fields. Rather, in ADO, you need to create a field as a picklist in...
Jerrold Emery over 2 years ago in Azure DevOps Services and Server 0 Future consideration

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

Filter Slack notifications based on votes

What is the challenge? We get a large amount of posts every day that is too much for regular Slack integration. What is the impact? We don't use the Slack integration Describe your idea We'd like to only get Slack notifications when a post gets ab...
Guest 2 months ago in Slack 0 Future consideration

Allow for Lookup Fields to be mapped in SFDC integration

Who would benefit? Everyone What impact would it make? Allows for further data collection from SFDC in Aha! How should it work? Similar to how other SFDC fields are currently mapped in today's configuration.
Guest 4 months ago in Salesforce 0 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

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