Skip to Main Content

Share your product feedback

ADD A NEW IDEA

My ideas: Integrations

Showing 944 of 9093

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

Integrate with Technopedia

Roadmap tool should integrate with Technopedia - Prior to Gartner "Acquiring" CEB and its road mapping tool, the State of CA and many other entities used it to first upload application product inventory, run "vendor data validation" against each p...
Guest over 1 year ago in Features / Integrations 0 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

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

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.
amy kennedy about 9 years ago in Integrations 2 Unlikely to implement

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

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!...
Guest about 6 years ago in Integrations 0 Future consideration

Broken Atlassian Webhook

Escalating this issue again here as it's now been moved to Atlassian's Long-Term Backlog & is critical to the adoption of Aha! at my company (as in people want us to go back to just JIRA bc syncing is so bad & data is out of date).  U...
Guest about 6 years ago in Jira 0 Future consideration