Skip to Main Content
ADD A NEW IDEA

Integrations

Showing 949

API - support sending multiple parameters/values in search query

The API currently only accepts a single value search parameter. There is a requirement to be able to pass multiple parameters/values through the API. For example, execute a search through the API for features that contain 3 specific tag values.
Matt Case over 7 years ago in Integrations 1 Future consideration

GitHub integration automatic log time upon linked issue completion

The intended use of GH integration is the following: Create features in Aha Push to GitHub as a handover of control to engineering Updates in GitHub trigger status changed in Aha This is a good start. If control is passed to engineering to manag...
Guest over 7 years ago in GitHub 2 Already exists

Ability to customize Aha panel in Salesforce

Today, we can customize almost everything in the portal we use in Aha-Salesforce integration, excluding the panel itself that is shown in Salesforce. I would like to be able to: custom the wording of the fields there - e.g. if in the portal I rena...
Ronit Binshtok almost 2 years ago in Salesforce 0 Future consideration

Tickets linked to JIRA should link back to Aha.

We are currently pushing Aha! tickets into JIRA. It would be helpful to have a link in Aha-created JIRA tickets that linked back to Aha (the same way Aha! has a ticket number and link to the JIRA ticket).
Guest over 7 years ago in Jira 0 Already exists

Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship.

Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship. Same like Jira we have parent -child relationship concept of subtask we need in Aha same functionality.
Guest almost 4 years ago in Jira 3 Already exists

Need to be able to connect Google Drive files

Looks like Aha! is not approved by Google's application security process? This is a huge issue for us as we are in the middle of planning for upcoming quarters and using Aha! for the first time. Is this likely to be fixed in the future? Is there a...
Shosh almost 2 years ago in Integrations 2 Will not implement

Properly transfer images in VSTS comments to Aha!

Currently, if a user adds a comment to a User Story or Bug discussion in VSTS and embeds an image in the comment, the image doesn't come through with the comment that shows up in Aha!. This makes it difficult for the reader in Aha! to follow the d...
Guest almost 6 years ago in Azure DevOps Services and Server 0 Future consideration

Filter capabilities on the Integration Update Import screen

As one Product Owner of a very large product that has a lot of product owners, I would like more filter capabilities on the Integration Updates import screen so that I can only see items that pertain to my portion of the backlog. This request is s...
Guest almost 2 years ago in Azure DevOps Services and Server 0 Future consideration

Have the PERT Chart

Hi, Is it possible to have the PERT chart based on the Gantt chart created for a product ? With that it will be more easy to work on the critical path. Thank you.
Guest almost 6 years ago in Wanted 0 Future consideration

Support bi-directional flow of data when mapping Aha! releases to Jira sprints as a field mapping for features

Use case: Aha! releases are mapped to Jira sprints as a field mapping under features. Currently this mapping is only supported in one direction, Aha! to Jira. It would be helpful if this mapping supported the flow of data in both directions.
Dale Potter almost 4 years ago in Jira 0 Future consideration