Integrations
Sort by:
Trending
Status:
Showing 954
3
VOTE
Reload configuration for all child integrations when a template integration mapping is updated
If you have an integration template with mappings that are inherited by child integrations, you can adjust the mapping step on that integration template to propagate your new mapping to all the integrations using that template. If you are doing so...
0
Future consideration
31
VOTE
Jira sprint dates as feature end dates
With the Jira integration it is possible to pull through the Sprint name as a custom field into Aha Master Features/Features. It would be useful to be pull through the sprint finish date and apply that to all linked items within Aha. This would al...
4
Future consideration
15
VOTE
Jira integration user name
In both Jira and Aha!, you need to have a user that has the appropriate permissions which is often a highly privileged user. However, when setting up the integration, there is no way to indicate an alias name to use for the integration. Consequent...
0
Future consideration
1
VOTE
Update blank Jira fields on import to Aha! even if they are set up as a two-way sync
Currently only fields that are mapped one-way from Aha! to Jira will update when imported to Aha! - we import records from Jira to Aha! without a version set in Jira and Aha! automatically adds them to a default release in Aha! - we would like Aha...
0
Future consideration
3
VOTE
Adjust sync direction for URL fields in integration mappings
What is the challenge? When a URL custom field is referenced within field mappings of an integration, it can not be set to update from the integrated system to Aha! only from Aha! to the integrated system. What is the impact? We can not adjust dir...
1
Future consideration
25
VOTE
Including Attachments from Comments for Jira Integration
It would be useful if we had the ability to push attachments made on comments, to Jira. Today, only direct attachments (to features or requirements) are supported, but from a UX perspective, attachment from comments should be included too, OR an a...
4
Future consideration
37
VOTE
Integrations 2.0: Add dependency link to connect records without natural relationships together
In integrations 1.0 if I mapped Features = Story Requirement = Task Aha! would send the records to JIRA and create a "Relates to" dependency between the Story and the Task to visualize in JIRA that the two records should be related to each other. ...
3
Future consideration
20
VOTE
12
VOTE
Provide alternative way to match users when email address is not exposed in Jira
Some time ago, Atlassian made changes that requires users to share their email addresses on an individual user profile setting. When that option is not checked, Aha! is not able to view their email address and if assigned user is mapped, is not ab...
1
Future consideration
27
VOTE
Allow a single Azure DevOps webhook to support updates across multiple Aha! integrations
With Jira, a single Aha! webhook added at the system level supports updates across all Aha! integrations.
This makes scaling integrations simple as after the first setup, a user never has to add another webhook.
With Azure DevOps (TFS), each i...
1
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved