Integrations
Sort by:
Trending
Status:
Showing 945
2
VOTE
Allow GitHub EE synchronization to filter by label
As an Aha user and git user I often want to sync certain stories or issues from github but not others. introducing a filter by label would allow me to sync a subset of issues only and avoid the confusion of task and bug issues in my Product tool. ...
1
Future consideration
1
VOTE
Differentiate the import of Salesforce Accounts
We have 000's of Organizations in our Aha instance and recently configured an integration with Salesforce and mapped multiple custom fields. On 'Integration updates', it would be helpful to know what would be an update to an existing Organization ...
2
Future consideration
3
VOTE
Add filters to integrations to prevent sending records that meet criteria
It would be useful to be able to create filters to prevent certain records from being sent to Azure, JIRA, or other integrations. For many workflows, there may be "raw" working records in a release backlog that are not ready to go to engineering t...
2
Future consideration
1
VOTE
Conditional Notifications for Activities & To-dos
Aha! needs more robust notification functionality—particularly, conditional formatting. We use Aha! to manage GTM activities associated with product launches. I would like to use Aha! to send automated reminders/alerts to activity & to-do assi...
0
Future consideration
4
VOTE
1
VOTE
Confluence link to List Report is not updating properly
I created a List Report in Aha and output to a webpage which I then embedded in a Confluence page using the Confluence Aha App. I made a change in Aha to the title of a Feature and the change was not reflected in the Confluence page embedded webpa...
1
Already exists
4
VOTE
For Jira integration, enable ability to prevent releases being automatically created in Jira (and/or enable this for releases in parking lot)
Right now we have an integration set up between Jira and Aha (which is extremely useful). However, whenever a feature in Aha that's linked to an issue in Jira has its release updated (e.g. moved from "v1.12.0" to "Backlog"), if the release to whic...
0
Future consideration
6
VOTE
Integrate existing FogBugz cases into Aha! as features (similar to JIRA 2way integration)
This will allow teams that use FogBugz to onboard to Aha! easier, without having to orphan FogBugz cases already entered that cannot speak back to Aha! through the current FogBugz integration.
2
Unlikely to implement
4
VOTE
Be able to bulk update only rank or a single field within JIRA integration
Normally our product managers works on Initiatives in Aha! by editing/ranking them. Those field changes and ranking will sync to Jira backlog for architect team to work on follow priority of Initiatives. When a rank is changed for a record in Aha!...
0
Future consideration
1
VOTE
Inform user if Version export to Jira fails due to existing fix version in Jira
Problem If a Version is exported from Aha to Jira using the integration, and a fix version with that same name already exists in Jira, Jira will response with HTTP status code 400, and a JSON payload: {"errorMessages":[],"errors":{"name":"A versio...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved