Integrations
Sort by:
Trending
Status:
Unlikely to implement
Showing 938
133
VOTE
1
VOTE
Option to enable "bypassRules" for Azure DevOps integrations
What is the challenge? ADO projects can have work items rules in place that prevent the Aha integration from working. For example, the ADO state transitions may be restricted by values in other fields. What is the impact? In order to prevent the r...
0
1
VOTE
42
VOTE
Rally Project name change should be reflecting in the Aha! Integration
What is the challenge? Rally Project name is updated but the project name is not updating in the Aha Integration Project Tab? What is the impact? Users see the wrong project name in the Aha integration and think they need to create a new integrati...
1
Already exists
1
VOTE
Slack message when Idea is Created
What is the challenge? In Slack 2.0 integration there's no "Idea Created" option to send the idea to Slack when the user is creating idea. What is the impact? Large Describe your idea When configuring Slack message via the integration, please add ...
0
Already exists
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
2
VOTE
Automation rule to update already integrated records
Currently, automation rules provide the ability to send an Aha! record through an integration based on the record being updated in a specific way. We would like for the ability to push updates to already integrated records in the same way. This is...
0
Likely to implement
23
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
Record successful updates in Aha! from Jira "update records" action
What is the challenge? Currently, there are log events for successful updates made from Jira when using the "Update Records" action What is the impact? Users have no way of knowing which records were successfully updated and what fields were chang...
0
Future consideration
3
VOTE
Include Record IDs when logging Update Record sync errors
What is the challenge? When users use the "Update Records" action in the Jira integrations, sync failures are logged as Sync errors without mentioning which record failed to update What is the impact? Users are not able to troubleshoot and address...
0
Planning to implement