Integrations
Sort by:
Trending
Status:
Future consideration
Showing 633
2
VOTE
Integration between Aha! and SPM module of ServiceNow
What is the challenge?
Several teams in our org are using SPM to manage their project works and roadmaps, and they are seeking for easy way of integrating those data within the tool with Aha.
What is the impact?
No integration tool to easi...
0
Future consideration
1
VOTE
Custom field added to Integration import notification window
What is the challenge?
I have to sift line by line through integrations in order to import only what I want and ignore what I don't want
What is the impact?
time=consuming with a large volume of features
Describe your idea
Allow me t...
0
Future consideration
4
VOTE
Add ability to restrict auto import of parent record with ADO
What is the challenge?
When importing features from ADO the parent epic is automatically brought into Aha! Epics can live in separate projects and the team does not always want them to display within Aha!
What is the impact?
Difficulty in ...
0
Future consideration
67
VOTE
Add Rally "Project" field to integration reports
What is the challenge? What Project Name is an integration connecting to for Rally Integrations What is the impact? Cannot create a list report showing what Project Name is an integration connecting to in Rally Describe your idea Add the 'Project'...
3
Future consideration
11
VOTE
Jira integration - Allow Jira account username/password modification per workspace when using a shared integration template
What is the challenge?
We have a shared template across all of our Jira integrations to manage the configuration globally. However, using a global template forces us to have the same integration username (mine, the Aha!/Jira admin) across all pr...
4
Future consideration
6
VOTE
Support for Jira Expand and other Macros in Aha!
What is the challenge?
Currently, Aha! does not support expandable macros (e.g., collapsible sections) coming from Jira Description.
What is the impact?
This leads to significant data loss — important contextual information, formatting, or...
0
Future consideration
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
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
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
© 2025 Aha! Labs Inc.•All rights reserved