Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Azure DevOps Services and Server

Showing 108

Inherit the hierarchy of the area paths from Azure Dev Ops

When integrating with Azure Dev Ops, the area paths should inherit the same hierarchy when represented in Aha. For example, hierarchy in Dev Ops could be: Company/ Company /Functional Area Company/Functional Area/Team The Aha Azure devops integrat...
John M over 4 years ago in Azure DevOps Services and Server 5 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 9 months ago in Azure DevOps Services and Server 0 Future consideration

Allow mapping fields from related records in Aha to Azure Devops

This idea is to allow mapping fields from related records from Aha to DevOps. In most cases, this would be parent/grandparent/great grandparent situations. For example, allowing a tag from an Aha feature to be mapped to a tag on a DevOps PBI. Anot...
Josh Wayne about 3 years ago in Azure DevOps Services and Server 0 Future consideration

Include Investment Types for Release In Integration

What is the challenge? For Releases Investment types are not supported in Integration Set Up How would you solve it? Manually Project Managers are adding in Devops What impact would it make? It will reduce so much of manual work
Guest 10 months ago in Azure DevOps Services and Server 0 Future consideration

Include Attachment for Release In Integration

What is the challenge? For Releases Attachments are not supported in Integration Set Up How would you solve it? Manually Project Managers are uploading in Devops What impact would it make? It will reduce so much of manual work
Guest 10 months ago in Azure DevOps Services and Server 0 Future consideration

Include Attachment for Release In Integration

What is the challenge? For Releases Attachments are not supported in Integration Set Up How would you solve it? Manually Project Managers are uploading in Devops What impact would it make? It will reduce so much of manual work
Guest 10 months ago in Azure DevOps Services and Server 0 Future consideration

Update records selectively

The "Update Records" feature currently updates all integrated records defined in the Azure DevOps integration. This could take quite some time if the number of records is high. Sometimes you only want to upgrade on a particular record type because...
Guest about 4 years ago in Azure DevOps Services and Server 0 Future consideration

Allow VSO integrations to work with multiple Aha Products represented in a single VSO Project

Some customers have specified that they maintain a single VSO Project, but represent a number of products beneath it. The way to handle that now in Aha is to set up a web-hook for each product in Aha, and then create a subscription in VSO that fil...
Alex Bartlow about 9 years ago in Azure DevOps Services and Server 1 Unlikely to implement

Sync the change of parent link made in Aha! across 2 Azure DevOps integrations

Who would benefit? Customers with multiple integrations set up to ADO who are wanting to move features to different Epics as their plans change. What impact would it make? How should it work? The parent/child relationship should be tracked across ...
Stuart Blair 10 months ago in Azure DevOps Services and Server 0 Future consideration

Sync sprints between requirements in Aha! and equivalent (e.g. PBIs) in Azure DevOps

Our development team manages PBIs within sprints. Currently you can map a custom sprint field for features in Aha! to DevOps, but not requirements. Ideally, we would be able to sync sprints for requirements/PBIs, as that would be more useful than ...
Mike Maylone over 4 years ago in Azure DevOps Services and Server 0 Future consideration