Integrations
Sort by:
Trending
Status:
Showing 923
11
VOTE
Support an integration with BetterWorks to sync goals, success metrics and initiatives
As a company adopting a next generation performance management system anchored in the concept of Objectives and Key Results I would like to synchronize Aha goals, success metrics and initiatives with BetterWorks (www.betterworks.com)
Note: both B...
0
Unlikely to implement
2
VOTE
Idea integration with Vivun Hero's Opportunity Gap functionality
Vivun Hero is a presales-focused bolt-on to Salesforce which allows SCs/SEs to tie product gaps to opportunities -- to provide reporting to Product on revenue at stake with those gaps. Having a more direct integration to be able to tie Aha! ideas ...
0
Future consideration
5
VOTE
Jira Sync Aha Release Phases and To-Dos
Please enable the ability to sync a release phase to an Epic in Jira. And also sync release phase To-Dos to tasks in Jira. Use Case: I have a release template with my release phase and associated to-dos. These to-dos are what govern my Jira tasks....
0
Future consideration
7
VOTE
Show comments added in JIRA as part of a state transition.
Currently, when a comment is add to a JIRA issue as part of a state transition, the comment is not shown in AHA.
This is a real issue for us since the Engineering team adds useful comments in JIRA when they move an issue between states. This mean...
2
Future consideration
7
VOTE
Add Product Name to JIRA Integration
The Product Name contains an import department work categorization that we would already use to filter reports in Aha and would like to be able to do the same in JIRA. There is a similar request to have Product Name in the Slack integration. I won...
0
Future consideration
5
VOTE
Update records selectively
The "Update Records" feature currently updates all integrated records defined in the Azure DevOps integration. This could take quite some time if the number of records is high. Sometimes you only want to upgrade on a particular record type because...
0
Future consideration
8
VOTE
Pivotal Tracker Integration Mapping
It would be helpful if one of the mapping options with Pivotal Tracker could include the following options:
Master Feature to Epic
Feature to Story
Requirement to Task
Instead, the only option for mapping to Epics in PT is to use Initiativ...
1
Future consideration
1
VOTE
Allow one-way mapping of calculated/read only Jira fields into Aha
Who would benefit? Aha users needing to see Jira data that is not editable in Jira What impact would it make? In our case, allow us to use engineering estimation data in Aha scorecard calculations. How should it work? The current Aha-Jira integrat...
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
2
VOTE
Aha! Releases Should Honor ADO Area by Default
I am unsure why this feature was designed this way; However, when creating and pushing a release from Aha! to ADO, it should honor the area path set up in the Aha! to ADO integration. Furthermore, when linking to an existing iteration in ADO, the ...
0
Future consideration