Integrations
Sort by:
Trending
Status:
Shipped
Showing 954
12
VOTE
Configure AHA! to support GSuite - sheets, slides, docs, etc.
We are a company that uses GSuite, this would allow us to pull data into our collaborative space and manipulate reports to personalize further than what AHA! current allows. Currently the inability to use AHA with GSuite causes delays and setbacks...
0
Future consideration
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
3
VOTE
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...
0
Future consideration
5
VOTE
Populate Jira Components via Integration
Currently, as far as I am aware, the only way to use Components from Jira is to add a custom field in Aha! and map them. This works OK, however if a new component is added in Jira you have to manually add it to Aha! as an option to select. Please ...
0
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
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
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
3
VOTE
Support mapping Asset object fields through Jira integration
Who would benefit? Customers using the Asset object through Jira Service Management. What impact would it make? When these Asset fields are added to Jira issue screens, this would allow users to map these fields to Aha! fields through the Jira int...
0
Future consideration
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
© 2025 Aha! Labs Inc.•All rights reserved