Integrations
Sort by:
Trending
Status:
Likely to implement
Showing 947
2
VOTE
Sync @ Mentions With Linked JIRA Users
Useful to keep users of JIRA and Aha in sync between systems without managing Watchers across installations.
I've noticed that @ mentions in Aha! do not match the JIRA username on comments. I want to ensure that JIRA users are notified when I @ me...
0
Unlikely to implement
2
VOTE
Add idea integration with Parature
We use parature as our system for managing customer support tickets including logging bugs. We would like the ability to push customer logged bugs from Parature directly to Aha so that customers can be made aware of bugs logged by other customers,...
0
Unlikely to implement
2
VOTE
1
VOTE
"Do you want to sync features as well?" (for Jira/Aha integration)
In my organization we need to sync features and releases in Aha to two different Jira projects. One project receives 100% of the features and releases - perfect 1:1 sync. But the other project is only for features that rely on the design team. So ...
3
Unlikely to implement
1
VOTE
Show Integration Errors Next To Integration Link
So often tickets stop syncing between JIRA & Aha! for one reason or another and yes, I understand there is an Integration Updates modal, but when you are working in a ticket, I should get a little error icon next to the link, in the record, if...
0
Future consideration
2
VOTE
Map user profile pictures from Salesforce community to Aha Ideas portal!
We want a seamless experience for our customers that are logged into our Salesforce community. Users have the ability to set their avatars in the Salesforce community but when they flow into the Aha ideas portal their avatar is not transferred ove...
0
Unlikely to implement
1
VOTE
Ability to execute a AzureDevOps query and display results in charts on Aha Dashboard
For the teams who uses AzureDevOps as ALM tool , It would be great flexibility to view a snapshot of the query results on the Aha dashboard. It does not need to be sync but can be pulled async.
0
Future consideration
1
VOTE
Allow TFS integration to map bidirectionally for fields that are not in a built-in System.State.
Currently, the TFS integration does not support mapping arbitrary string fields to the Aha! workflow status field in a bi-directional way. Only the built-in System.State field in TFS can be mapped bidirectionally.
2
Future consideration
1
VOTE
1
VOTE
Release Should Be Marked as Shipped only when all Integrations for JIRA projects are shipped
If multiple integrations are enabled at release level, allow workflow rule for release to be considered as shipped when all integrated JIRA projects have shipped the release If someone marks the release as shipped in JIRA, its changing the status ...
0
Unlikely to implement
© 2024 Aha! Labs Inc.•All rights reserved