Integrations
Sort by:
Trending
Status:
Future consideration
Showing 944
1
VOTE
Sync the change of parent link made in Aha! across 2 Azure DevOps integrations
Who would benefit? Customers with multiple integrations set up to ADO who are wanting to move features to different Epics as their plans change. What impact would it make? How should it work? The parent/child relationship should be tracked across ...
0
Future consideration
6
VOTE
Not able to map Aha Product Relationship field to Rally using Aha & Rally Integration
There is a need for us to add a Aha Product Relationship field to Rally using Aha & Rally Integration.
When we tried to add it to the mappings, we cannot see that field as part of field mappings to map to a Rally string field.
0
Future consideration
3
VOTE
New "integration reference" custom field type to house read-only text reference to a field on other side of Jira (or other) integration
There are fields in Jira (and I imagine other integrated applications) that don't map cleanly to an Aha custom field type. I am proposing a new custom field type that is an always-readonly text field that can be mapped to any Jira field type, and ...
0
Future consideration
10
VOTE
Removing account link from an idea in Aha! should remove the link on the account in Salesforce
Using the Salesforce integration, if you remove the request on the Idea page (by clicking on the bin icon) and go to the related account in Salesforce, the request is still listed there. Ideally this would update Salesforce dynamically.
0
Future consideration
1
VOTE
Defect: Jira Integration record mapping doesn't use custom terminology
Who would benefit? Anyone with custom names for "Epic" or "Feature" who is setting up a Jira integration. What impact would it make? Prevent failure of the integration (which took us several hours to figure out). This was particularly egregious fo...
0
Future consideration
1
VOTE
Allow project access token to be used instead of personal token for GitLab integration
Who would benefit? anyone using the integration with aha and GitLab What impact would it make? improves resiliency and stability of the integration How should it work? Currently, to set up the GitLab integration a user in GitLab must use a persona...
0
Future consideration
1
VOTE
Iteration to Release not Retaining Parent Relationship with other Records (AzDo Integration)
Who would benefit? Aha users What impact would it make? Elimination of lost records (Azdo integration) How should it work? When using iteration to release, the integration would look at the area path of that record as well as the iteration path. S...
0
Future consideration
5
VOTE
Include Jira Dynamic Dates in API
When integrating AHA / Jira the field mapping only shows fields that can be editable. We are looking to bring in Created Date and Resolved Date on both the Jira epic and Jira story. These fields are dynamically created and populated based on the f...
0
Future consideration
6
VOTE
Better display of user info from Jira integration
When comments are added to Aha from the Jira integration, they show up as having been created by Integration: Jira even though the comment includes the following:
Created in Jira by Matthew Monahan (****@****.com)
When I dig into the values in t...
0
Future consideration
8
VOTE
Exclude fields from Slack integration
Currently, the default value sends all fields. If I want to send all fields except, for example, "private comments" from the ideas portal to a dedicated ideas channel in slack, I have to add all the fields except "private comments" manually.
In...
1
Likely to implement
© 2024 Aha! Labs Inc.•All rights reserved