Integrations
Sort by:
Trending
Status:
Future consideration
Showing 630
24
VOTE
Update legacy domain for Azure
ADO integrations are sending to legacy domain "https://fredwin.visualstudio.com" instead of sending to "https://dev.azure.com/fredwin". Though the integration works as expected, clicking the link to the integrated record sends to the incorrect dom...
1
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
2
VOTE
Ability to map editable choice lists in Aha! with the Jira Team field and support bi-directional sync
What is the challenge?
Bi-directional sync of the Jira team field is only supported for some Aha! custom fields
What is the impact?
Mapping to a predefined choice list is not ideal because it requires us to manually update and map each tea...
1
Future consideration
2
VOTE
Ability to map custom Initiative fields in Jira integrations
What is the challenge?
Currently you can add custom initiative fields to record layouts, but these fields are not available to map in the Jira integration.
What is the impact?
Unable to pass this information over to Jira
Describe your ...
0
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
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
3
VOTE
Allow defining preferred time unit when syncing estimates from GitHub
What is the challenge?
It is possible to map estimate and work done fields to a GitHub project custom number field. This works well with story points, but if you are using time for your units, your values automatically convert to minutes.
Wh...
0
Future consideration
1
VOTE
GitHub Integration - Migrate OAuth App to GitHub App
What is the challenge?
Because Aha does not have a GitHub App, but an OAuth App, my GitHub integration would require manual allow-listing of Aha's IP ranges.
What is the impact?
I may not be able to integrate Aha with my GitHub environment...
0
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
Integrations 2.0 for github should use org apps not user creds
What is the challenge?
The current approach requires setting up a "service account" in our SSO then authorizing a user to checkout the password to setup connections
What is the impact?
Setup friction less trust from security teams
Desc...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved