My ideas: Integrations
Sort by:
Recent
Status:
Shipped
Showing 331
7
VOTE
Features and Epics should move to integrated parent Release upon updates
What is the challenge? If you introduce Version<>Release mapping to an existing integration or you link a record to an existing Jira record, subsequent updates are creating a new Aha! release (linked to the Jira issues's Fixed Version) but t...
0
Shipped
1
VOTE
Support referencing JIRA ID / JIRA Key attribute in calculated columns
What is the challenge The JIRA ID and JIRA Key are reportable attributes within Aha! and they were recently updated so they could be filtered in the reports. However, I need to reference these fields for custom calculations. What is the impact? I ...
0
Shipped
9
VOTE
Allow switching between integration templates if they are integrated with the same project
What is the challenge? As part of a migration, we are planning to change existing integrations and switch from using "Template A" to "Template B". The challenge is that "Template B" is not available for selection unless it is integrated with the s...
2
Shipped
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
Shipped
5
VOTE
New "child" records not imported from Jira
What is the challenge? Records are being skipped in the Jira integration if they are linked to a parent record in another workspace. This happens specifically when the webhook to create the child record includes the parent record. What is the impa...
1
Shipped
3
VOTE
Support Azure DevOps integrations for parent and child records across workspaces
What is the challenge? When a parent or a child record is moved to another workspace in Aha! it will no longer update via integrations due to the child and parent existing in different workspaces in Aha! What is the impact? Integrations break when...
0
Shipped
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
Shipped
2
VOTE
Support parent/child relationships for records integrated on different tools or instances
What is the challenge? Scenario 1: A parent initiative in Aha! is integrated with Jira instance 1 A child epic in Aha! is integrated with Jira instance 2 Scenario 2: A parent initiative in Aha! is integrated with Rally A child epic in Aha! is inte...
0
Shipped
9
VOTE
Update Microsoft Teams integration to not use connectors
Microsoft is deprecating Office 365 Connectors: https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/ Please update the Microsoft Teams integration to support workflows or a new app entirely. De...
1
Shipped
13
VOTE
Update progress and link to integration on background jobs
What is the challenge? When I run the Update records utility for many integrations, the background jobs page does not show an updated progress for each job. Also, if the job fails there is no link back to the integration so I can quickly find and ...
1
Shipped
© 2025 Aha! Labs Inc.•All rights reserved