Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 945

Import functionality to show the entire list of records and have ability to import only selected (check box) records

Currently Rally import functionality shows only top 10 records extracted for the set criteria. Want the ability to see all the records with checkbox to allow 'pick & choose' for import Do not show the records which were already imported or linked
Jyothirmayi Talaparthy over 4 years ago in Rally 3 Future consideration

Fix sync of grid style between Aha and DevOps

We often create features in Aha and sync them into DevOps for the Dev Team. Our dev team then creates the user stories and syncs those back to Aha. They use a small grid in their user story template in DevOps. When it syncs back, that grid is oddl...
Guest almost 3 years ago in Azure DevOps Services and Server 0 Future consideration

Jira integration needs to include Tempo Team field

This is a blocker for us.
Tracey locke almost 3 years ago in Jira 1 Future consideration

GitHub Integration: Aha! Release to Github Release mapping

As a product manager setting up my GitHub integration, I want to map Aha releases to GitHub releases directly, to avoid confusing developers and make Aha adoption less painful.
Guest almost 6 years ago in GitHub 0 Future consideration

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. ...
Guest almost 3 years ago in GitHub 1 Future consideration

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...
Ronnie Merkel over 4 years ago in Integrations 2 Future consideration

Add warning text to Custom field Key field description that changing the key value will break integration

We found that changing the key-field string of a custom field will break existing integrations with ADO where the custom field is synced to an ADO field. There is no warning or anything. This is a big risk to us and to the trust that integration r...
Rob Boutmy over 1 year ago in Azure DevOps Services and Server 0 Future consideration

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...
Guest almost 6 years ago in Jira 0 Future consideration

Allow Jira Integration to synchronize External Release Dates

In Jira, we track external Release Dates. Aha does not allow external release dates to be synced. This means our Jira is reporting inaccurate information.
Guest over 1 year ago in Jira 0 Future consideration

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 ...
Jeff Shaffer over 1 year ago in Salesforce 2 Future consideration