Skip to Main Content
ADD A NEW IDEA

Azure DevOps Services and Server

Showing 101

Sync Release Phase to Azure DevOps

We have adopted a SAFe framework where features are planned quarterly. As a result we are creating 'Releases' in Aha that are materializing these quarters. Within a quarter we may deploy the software multiple times and we are using release phases ...
Nicolas Andrillon over 2 years ago in Azure DevOps Services and Server 0 Future consideration

Control how Estimates are converted and sent to TFS/VSTS

The default behaviour of how the TFS/VSTS integration sends time Estimates in minutes is very limiting. I don't know any agile team that would be estimating Features or Requirements down to minutes, so it doesn't make sense for the integration to ...
Guest almost 6 years ago in Azure DevOps Services and Server 1 Future consideration

Provide item ranking capability with Azure DevOps integration to Boards

Currently the Azure DevOps Boards integration does not include the capability to share the rank order of items in a workspace which results in the items in the Azure Devops Boards workflow having a different ordering than the items in the Aha rele...
Guest over 2 years ago in Azure DevOps Services and Server 0 Future consideration

Include author of comment from Azure DevOps when saving to Aha

We use the Aha <-> Azure DevOps integration. Comments from Aha include the author when synced to AzDO (Comment added by <user> in Aha! - View). The reverse is not true. Comments made in AzDO that come to Aha do not say the other, just ...
Guest about 1 year ago in Azure DevOps Services and Server 0 Future consideration

Ability to set Aha field to a constant value as part of integration field mappings

My scenario is that I have each Aha product linked to multiple different projects in Team Foundation Server (TFS), and I want the features in Aha that come from TFS to have a field indicating what TFS project they came from. But I can’t find a way...
Tessa Adair about 5 years ago in Azure DevOps Services and Server 7 Future consideration

Allow linking of Features and Releases to a specific DevOps Iteration Level

We use a more granular structure to the Iterations in DevOps so mapping items to just the top level is not really suitable to keep a feature synchronized correctly and could involve a lot of manual changes at the beginning and end of a release. Fo...
Dave Ball over 3 years ago in Azure DevOps Services and Server 2 Future consideration

Add support to map Azure Boolean Fields to Aha

This request is to support the mapping of ADO boolean fields to Aha predefined droplist and tag fields. Currently, Azure DevOps Boolean fields (true/false) cannot be mapped to Aha fields. Rather, in ADO, you need to create a field as a picklist in...
Jerrold Emery about 2 years 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 over 2 years ago in Azure DevOps Services and Server 0 Future consideration

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 3 years ago in Azure DevOps Services and Server 5 Future consideration

Aha! Releases Should Honor ADO Area by Default

I am unsure why this feature was designed this way; However, when creating and pushing a release from Aha! to ADO, it should honor the area path set up in the Aha! to ADO integration. Furthermore, when linking to an existing iteration in ADO, the ...
I R about 1 year ago in Azure DevOps Services and Server 0 Future consideration