Skip to Main Content
ADD A NEW IDEA

Integrations

Showing 945

Improving handling when Jira users change issue type across record hierarchy

Who would benefit? Users of Jira integration What impact would it make? Users who are changing issue types in Jira after records are integrated. How should it work? Right now, if a Jira user changes an issue type on an integrated record, the integ...
Stephanie Lechner 12 months ago in Jira 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 over 4 years ago in Integrations 3 Future consideration

Sync contact names in Salesforce integration

The names of the people we do business with is very important. The Salesforce integration should sync the contact names of our clients in Salesforce with the Ideas portal to enure consistancy and data consistancy.
Daniel Lynch almost 3 years ago in Salesforce 0 Future consideration

Keeping link to Jira when disable an integration

When we disable an integration to Jira, we mean it to be we have a new Jira project to integrate to. It makes it easier on the integration on the feature to not have a huge list of Jira projects to integrate to and only to the projects that are ac...
Carina Velazquez about 1 year ago in Integrations 2 Future consideration

JIRA: Detect default unit of time tracking

Aha! relies on time tracking in JIRA being set to the default value of minutes. If the value in JIRA has been altered to anything else, it throws time tracking estimates off. As of the 6.4.x version of the JIRA REST API a GET is available that ret...
Danny Archer about 9 years ago in Jira 12 Likely to implement

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), each i...
Guest about 5 years ago in Azure DevOps Services and Server 1 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 almost 3 years ago in Azure DevOps Services and Server 0 Future consideration

Merge on CSV import

What is the challenge? Multiple imports can cause duplicate entries What is the impact? Deleting duplicate entries is painfully slow since i could not find a bulk operation in Features list view Describe your idea Merge entries on import. Have use...
Guest 2 months ago in Integrations 0 Future consideration

CSV import is frustratingly archaic

What is the challenge? importing data is slow and tedious What is the impact? customers will get frustrated and abandon Aha Describe your idea The import process should be improved and use a little bit of AI to better match existing fields with cu...
Guest 2 months ago in Integrations 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 about 7 years ago in Wanted 9 Will not implement