Integrations
Sort by:
Status:
Future consideration
Showing 615
4
VOTE
Move epic/feature to default release when integrations unlink the release
What is the challenge? When an integrated epic or feature is moved in a dev tool (Jira or Rally) to an "unscheduled" release, the relationship in Aha! is null and no change occurs. This is problematic because the release was changed but the Aha! r...
1
Future consideration
3
VOTE
Activity webhook triggered by a specific custom field
What is the challenge? Our custom integration between Salesforce and AHA is not being triggered. What is the impact? Custom field is not updated in SF when it is the only field updated on an idea. Describe your idea Allow activity webhook configur...
3
Future consideration
25
VOTE
Azure DevOps Integration - Sync dependencies at UserStories/Requirements level
What is the challenge? Currently, Aha integration with ADO syncs dependencies at Features level only. We need to also be able to sync the dependencies at Requirements/UserStories level.Including dependencies between Features and User Stories. What...
0
Future consideration
3
VOTE
Add ability to set selected users for Slack notifications from Aha!
What is the challenge? Currently, the newest Aha! Slack integration does not allow you to set specific users to trigger a notification to Slack from Aha! in the way the previous version supported. What is the impact? You cannot filter down activit...
3
Future consideration
2
VOTE
Viva Engage (Yammer) ideas integration
What is the challenge? Ideas/Roadmaps integration with viva engage (yammer) similar to slack or teams integrations. What is the impact? We currently share updates from roadmaps and ideas with stakeholders and teams via yammer rather than teams. De...
0
Future consideration
10
VOTE
Seamless Sync for Epics and Features Between Aha! and ADO when changing types
What is the challenge? Currently, when an Epic is changed to a Feature or vice versa in Azure DevOps (ADO), this change is not accurately synced with Aha!, leading to misalignment and inefficiencies. What is the impact? Epics and features are misa...
1
Future consideration
239
VOTE
Integrate Aha! and Confluence to link Confluence Pages in AHA! and transfer them with JIRA
Atlassian currently offers the ability to Integrate Confluence & Jira using Application Links which gives teams multiple features. https://confluence.atlassian.com/doc/use-jira-applications-and-confluence-together-427623543.html One of the fea...
6
Future consideration
2
VOTE
Bi-directional support for Area Level fields in ADO integration
What is the challenge? Currently we offer Area Level fields in our ADO integration for each Area Level. This allows us to receive the unique Area Level from ADO, but currently updates in Aha! do not change the Area Level back in ADO despite the se...
0
Future consideration
3
VOTE
Adjust sync direction for URL fields in integration mappings
What is the challenge? When a URL custom field is referenced within field mappings of an integration, it can not be set to update from the integrated system to Aha! only from Aha! to the integrated system. What is the impact? We can not adjust dir...
1
Future consideration
172
VOTE
Dedicated Integration User
It would be great to have a dedicated integration user instead of having to use a user license for this purpose. I would love to keep my user and the updates from integrations (Jira, TFS,...etc) separate so that it is clear who made the update in ...
16
Future consideration