Skip to Main Content
ADD A NEW IDEA

Azure DevOps Services and Server

Showing 108

Handle multi-select fields in ADO integration

What is the challenge? Running into an issue where multi-select from Aha can't flow over to ADO multi-select field. Only first value flows over from Aha. What is the impact? Can't use multi-select field in ADO properly. Describe your idea Allow fo...
Alex Berestenko 18 days ago in Azure DevOps Services and Server 0 Future consideration

Bi-directional support for Area Level fields in ADO integration

What is the challenge? Currently we offer Area Level fields in our ADO integration for each Area Level. This allows us to receive the unique Area Level from ADO, but currently updates in Aha! do not change the Area Level back in ADO despite the se...
Stephanie Lechner 24 days ago in Azure DevOps Services and Server 0 Future consideration

Option to enable "bypassRules" for Azure DevOps integrations

What is the challenge? ADO projects can have work items rules in place that prevent the Aha integration from working. For example, the ADO state transitions may be restricted by values in other fields. What is the impact? In order to prevent the r...
David I. about 1 month ago in Azure DevOps Services and Server 0 Future consideration

Support Azure DevOps integrations for parent and child records across workspaces

What is the challenge? When a parent or a child record is moved to another workspace in Aha! it will no longer update via integrations due to the child and parent existing in different workspaces in Aha! What is the impact? Integrations break when...
Justin Paulson about 2 months ago in Azure DevOps Services and Server 0 Planning to implement

Seamless Sync for Epics and Features Between Aha! and ADO when changing types

What is the challenge? Currently, when an Epic is changed to a Feature or vice versa in Azure DevOps (ADO), this change is not accurately synced with Aha!, leading to misalignment and inefficiencies. What is the impact? Epics and features are misa...
Rob Stebbens 3 months ago in Azure DevOps Services and Server 1 Future consideration

Support configuring capacity units of time for ADO server integrations

What is the challenge? Currently the "Configure" option to select units of time to send estimates to ADO is only avaiable on the ADO Services integration and is not available for users using the Server integrations. What is the impact? Users are u...
Stephanie Lechner 3 months ago in Azure DevOps Services and Server 0 Future consideration

Azure DevOps Integration - Sync dependencies at UserStories/Requirements level

What is the challenge? Currently, Aha integration with ADO syncs dependencies at Features level only. We need to also be able to sync the dependencies at Requirements/UserStories level.Including dependencies between Features and User Stories. What...
Guest 5 months ago in Azure DevOps Services and Server 0 Future consideration

Text from Azure DevOps into custom fields shows with HTML elements

What is the challenge? When syncing a "text" custom field with Azure DevOps it shows the text with HTML elements What is the impact? It makes the custom field text difficult to read Describe your idea Ensure text custom fields convert HTML tags wh...
Guest 5 months ago in Azure DevOps Services and Server 0 Likely to implement

Enable tags to be a selection for Azure DevOps integration of requirements

What is the challenge? You can sync tags for features but not requirements, What is the impact? creates duplication of work having to recreate tags in Azure DevOps Describe your idea As part of the field mapping for Azure DevOps integration "tags"...
Guest 5 months ago in Azure DevOps Services and Server 0 Future consideration

DevOps Integration: button to receive all fields

What is the challenge? Possibility to easily refresh an item from DevOps What is the impact? In case of non-synchronized items, it will be easier to refresh the status from DevOps Describe your idea Currently, when an item is linked to a correspon...
Nicola Rolando 6 months ago in Azure DevOps Services and Server 0 Future consideration