Skip to Main Content
ADD A NEW IDEA

Azure DevOps Services and Server

Showing 99 of 8592

New features created via an ADO integration are assigned to the parent epic release by default

Key problem: the "Parent" field in ADO can contain only one value. In ADO, a feature is automatically associated to the same theme as its' parent epic, but in Aha! this is not the case. So when features import, we associate them with the correct p...
Bryan McElhinney over 1 year ago in Azure DevOps Services and Server 0 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 almost 6 years ago in Azure DevOps Services and Server 3 Future consideration

Support linking the Aha! URL field to the Azure DevOps Hyperlink field

Goal: We want to see in DevOps which Item it syncs with in Aha! Current set up: Aha! URL field linked to Hyperlink field in DevOps Challenge: We are using the hyperlink field to capture URLs to multiple sources. This is all being done in a single ...
Euan Callow over 2 years ago in Azure DevOps Services and Server 2 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 over 4 years ago in Azure DevOps Services and Server 2 Future consideration

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

VSTS Requirement ToDo's

Can we get the VSTS Requirement To Do's transferring over as user story tasks?
Guest over 7 years ago in Azure DevOps Services and Server 3 Future consideration

Integration to Azure DevOps for teams capacity planning

We would like to use Points based capacity planning but it needs to be integrated with (in our case) Azure DevOps which is where the team is committed to and working on work. All of our Features and Master Features (Epics) in Aha are calculated ba...
Heath McCarthy over 3 years ago in Azure DevOps Services and Server 2 Future consideration

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

Need full two way integration of a Story with VSTS

Right now you can push a Feature and associated stories to VSTS but if you delete a story in VSTS you have to manually delete in Aha. We need: 1) any story delete in VSTS to be automatically deleted in Aha 2) any story added in VSTS to a Feature...
Eric Reichel over 7 years ago in Azure DevOps Services and Server 1 Unlikely to implement

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