Skip to Main Content
ADD A NEW IDEA

FILTER BY CATEGORY

Azure DevOps Services and Server

Showing 81 of 7182

Allow Aha! user name to populate DevOps board user

When working with multiple users, we need to be able who created what, commented on or changed something. As of right now, the user name (Admin) of who configured the Integration (Azure DevOps Services) is the one that appears on every item in Dev...
Guest over 2 years ago in Azure DevOps Services and Server 3 Future consideration

Include Area Path in VSTS Integration

I really like the VSTS integration 2.0, however could you add Area Path to the list of available fields that can be mapped to. This would be useful as in VSTS we use Area Path to note which dev team has picked up a feature and it would be great to...
Guest about 4 years ago in Azure DevOps Services and Server 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 7 months ago in Azure DevOps Services and Server 0 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 7 months ago in Azure DevOps Services and Server 0 Future consideration

VSTS Requirement ToDo's

Can we get the VSTS Requirement To Do's transferring over as user story tasks?
Guest almost 6 years ago in Azure DevOps Services and Server 3 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 11 months 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 about 2 years ago in Azure DevOps Services and Server 5 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 about 2 years ago in Azure DevOps Services and Server 2 Future consideration

Allow two-way integration for picklist fields in Azure DevOps when using the XML process model

This idea is a variation on https://big.ideas.aha.io/ideas/AFME-I-2, but the general use case is the same. I've been asked by Aha support to make a separate idea specifically for those using the XML process model, since this has supposedly been fi...
Tessa Adair over 1 year ago in Azure DevOps Services and Server 0 Future consideration

Allow additional Link Types in the 'Links to' field

Within AHA we are mapping Releases -> ADO Release Work Item Master Feature -> ADO Epics Features -> ADO Features. Master Features need to be located in the Release in which they complete. But Features (that contribute to this M...
Guest almost 3 years ago in Azure DevOps Services and Server 1 Future consideration