Integrations
Sort by:
Recent
Filter by:
Status
Showing 849 of 8120
19
VOTE
4
VOTE
Filter noise from Jira integration logs
The log file currently reports on Jira tickets that are out of scope for the integration (e.g., bugs, stories, tasks) as defined by the integration template. These log entries typically end with "No changes made in Aha!" If I'm trying to find the ...
0
Future consideration
1
VOTE
Allow link of a requirement to a release (sprint)
We have features that are mapped to a specific sprint, but within that feature, we have requirements (user stories) that could be mapped to two different sprints. The assumption with Aha! is that a feature would be completed in one sprint, which i...
0
Future consideration
3
VOTE
8
VOTE
Associate the Salesforce Account ID with Aha! ideas portal users via SSO
Some of my customers work for large organizations that we have broken down into many accounts in Salesforce. The customers who access the idea portal are associated directly with the Salesforce account and that account might have the same email do...
2
Future consideration
2
VOTE
Publish updates to a Kafka Topic
When looking at an integrated planning view, including Jira epics/stories/backlogs for upcoming work in addition to current work test results, we'd like to join data from multiple tools, and view current status across multiple tools. If we use the...
0
Future consideration
1
VOTE
Calculate Epic Completion Based on JIRA Epic Completion
The options to calculate the completion of an epic in Aha is only based on user stories, but there are other items in JIRA that determine how complete an epic is. It would be helpful to have the progress bar completion automatically reflect whatev...
0
Already exists
1
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
4
VOTE
Update the Feature % Complete field based on User Stories of the DevOps Feature
Update the Feature % Complete field based on User Stories of the DevOps Feature that is linked to the Aha Feature. The Software Product Plan does just that! In DevOps, this information is a calculated field, which can be easily configured in Board...
1
Future consideration
1
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