ADD A NEW IDEA

Integrations

Showing 640

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

Hover text on Jira integration to show project & board

In workspace settings, once an integration is established, it would be nice to be able hover over the integration and see at a glance the project and board without clicking into the integration and looking at the project/board setup.
Guest almost 2 years ago in Jira 0 Future consideration

Add ability to customize the "Integration updates" modal

Request the ability to customize what is displayed and in what order on the "Integration updates" modal. We are integrated with Azure DevOps (ADO) Services, so our specific request is to display the ADO ID at the top level on this modal. It will m...
Guest almost 2 years ago in Azure DevOps Services and Server 0 Future consideration

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 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

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 over 7 years ago in Integrations 1 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

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 over 5 years ago in Wanted 0 Future consideration

Feature Email update notification to include link direct to Jira record

From a time saving point of view it would be really handy to include the Jira link in the email notification that comes when an item is updated. This field/link already exists within the feature itself so should be easy enough to add in to the ema...
Scott C over 5 years ago in Jira 0 Future consideration