Integrations
Sort by:
Trending
Status:
Future consideration
Showing 950
15
VOTE
Lock down integration templates
We have almost 200 integrations based on 1 template, and users are going in and mistakenly modifying the template which is locking other users out.
We would like to only Admins to be able to change the template, including the Based on Template ch...
1
Unlikely to implement
15
VOTE
Link Salesforce opportunities to Features
Today, the SFDC integration can only link opportunities to ideas. It would be great to also link to features. This could help prioritize features that are still in a parking lot and would reduce the buden of merging ideas created via SFDC with exi...
2
Future consideration
2
VOTE
Enable tags to be a selection for Azure DevOps integration of requirements
What is the challenge? You can sync tags for features but not requirements, What is the impact? creates duplication of work having to recreate tags in Azure DevOps Describe your idea As part of the field mapping for Azure DevOps integration "tags"...
0
Future consideration
2
VOTE
Ability to import child records when connecting to an existing record in Jira
What is the challenge? We often have the use case where we need to connect an Aha! epic to an existing Jira record, and that Jira record will also likely have child tasks/stories. The existing connection logic will only sync with the epic record, ...
0
Future consideration
7
VOTE
Fix field population in Aha/Jira integrations to only rely on email address or other specific data
Today when the Aha/Jira integration runs it looks up users in Jira based on email, then failing to find a match it checks first name, then last name. Jira returns results for these and Aha will select the first return. The problem is that if we ha...
1
Future consideration
12
VOTE
Ability to copy/move an integration template
We would like to be able to copy and move an integration template from one workspace to another. This would allow us to restrict access on the template if we could move it to a location that no regular users have access to. We can then use that te...
4
Future consideration
25
VOTE
Allow To-Do's to be mapped to JIRA Issue Types
We would like to be able to make better use of Aha To-Do's so that they carry over to our JIRA Agile installation. Currently we have Initiatives mapped to Epics, Features Mapped to Stories and Requirements Mapped to a custom JIRA type of Requireme...
5
Unlikely to implement
25
VOTE
Work with Confluence for PRD Documents
Currently we use Confluence PRD documents: https://confluence.atlassian.com/display/DOC/Product+Requirements+Blueprint It would be great if we could find some way to combine this with Aha. Otherwise, we spend time duplicating information from insi...
11
Already exists
5
VOTE
6
VOTE
Filter capabilities on the Integration Update Import screen
As one Product Owner of a very large product that has a lot of product owners, I would like more filter capabilities on the Integration Updates import screen so that I can only see items that pertain to my portion of the backlog. This request is s...
1
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved