Integrations
Sort by:
Trending
Filter by:
Status
Showing 994 of 9673
1
VOTE
Allow the assigned to User to be sync'd with Jira
What is the challenge?
When assigning features in Aha that are then sync'd to Jira - the assignee field cannot be set
What is the impact?
When development teams use Jira and Product teams use Aha, the feature becomes the common currency. T...
0
Already exists
149
VOTE
Salesforce shows all ideas requested by a customer
When a customer submits an Idea in our Customer facing portal the Idea should be linked automatically into that users account on SalesForce, Today we are able to go into SFDC and manually search for the Idea for that user and link the account to t...
12
Likely to implement
1
VOTE
Guidance for which field types are compatible for mapping between Aha! and ADO
ADO and Aha have different field type definitions and only some are compatible. Example: pre-defined choice list isn't allowed for integration - must be an editable choice list. Or it can be pre-defined, but on ADO it has to be "xxx" type of field...
0
Future consideration
2
VOTE
Enable Aha Roadmaps Confluence Cloud macro to support 'static rendering'
What is the challenge?
The Confluence macro for Aha Roadmaps is no longer insertable inside other macros such as filterable table macros, as was possible in Confluence Data Center. This is due to a requirement for 'static rendering' support in C...
0
Future consideration
208
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
14
VOTE
Improve syncing fixed workflows with integrations
What is the challenge? When statuses are mapped as bi-directional in integrations (Jira etc.) - transitioning rapidly between statuses in a fixed workflow in Aha! does not send each transition to the dev tool. With a fixed workflow in the dev tool...
2
Future consideration
14
VOTE
Sending child records to one ADO project should not error out if parent record is integrated to a different Workspace and ADO project
What is the challenge? Users are now able to support linking work between multiple Aha! workspaces and multiple ADO projects with parent/child relationships spanning this; however one scenario is producing an error. When a parent record is integra...
1
Likely to implement
28
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
10
VOTE
Fix date syncing between Aha! and ADO
What is the challenge? Dates added on AHA/ADO are not properly synced and show up on the other tool as +/- 1 day as a result of time differences between the two tools. Expected behaviour: When selecting a date in one tool, the same date appears in...
2
Future consideration
133
VOTE
© 2025 Aha! Labs Inc.•All rights reserved