Skip to Main Content
ADD A NEW IDEA

Integrations

Showing 918 of 8649

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 over 3 years ago in Jira 0 Future consideration

Ability to search on the Jira Key

We have many users that have asked me for the ability to search for a Feature based on it's Jira Key. Currently the only way to do that using the Search box is for them to add the Jira Key to the Feature description, and they don't want to have to...
Guest over 5 years ago in Jira 1 Already exists

Parent version mapped to 2 different releases - let user decide where to import

The same Jira version may be associated with releases from more than one Aha! workspace. This can happen when different products in Aha! are all being released together. When auto-import is enabled on the integrations and a new record is created i...
Mark Crowe over 3 years ago in Jira 0 Future consideration

Allow for all lowercase "emailaddress" SSO attribute

Per the SSO documentation, Aha! supports multiple variations of uppercase/lowercase for the "EmailAddress" field, but we don't support "emailaddress". It would be great to support this, as "firstname" and "lastname" are allowed. I ran into this wi...
Emily Yankush almost 2 years ago in Integrations 0 Future consideration

Integrate with Avion (story mapping)

I love aha for so many reasons, but we use Avion for our story mapping. It's come up many times that we would love an integration with them so we can push our validated ideas into Avion. Please consider! I've asked the avion team and they are open...
Guest almost 2 years ago in Integrations 0 Unlikely to implement

Allow Integration variable on Create Record layout

Currently when creating a feature, I have to create the feature and then manually send the integration to ADO. I want to have a variable on the Create Record Layout screen to be able to choose this option when creating the feature. This way I can ...
Kalyndra Craven over 3 years ago in Azure DevOps Services and Server 0 Future consideration

Support JavaScript in the Salesforce integration

The Idea form does not currently support JavaScript when loading in the pop-up window as part of the Salesforce integration. We are using JavaScript to inject additional guidance in an HTML block, and would like to include some additional script t...
Michael Bruner almost 2 years ago in Integrations 0 Future consideration

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 over 5 years ago in Azure DevOps Services and Server 0 Future consideration

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 about 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 about 7 years ago in GitHub 2 Already exists