Azure DevOps Services and Server

What is the challenge? There is a tool to aid users in migrating from Jira server to Cloud, but it does not currently support ADO migrations. What is the impact? Users who need to migrate ADO have a manual process to relink records after moving to...

Epics on top of feature were introduced with VSO a few weeks ago. The VSO Connector should be able to reflect that somehow. Either by also working with epics in aha that encapsulate features or better the easy MVP way with a global setting for the...

We currently have to use the Feature Board in Aha! to prioritize the features. and then we have to use the Feature Board in TFS to apply the same order. The Feature Rank is not included in the integration with TFS. We need a process that synchroni...

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...

TFS import should create a link between Aha! features (and requirements) and TFS issues so that when we import to seed the Aha! account, we can keep the entire history of the TFS issue.

This is critical in order to sync the priority for TFS features with the priority of Aha features. There is a need to update the Business Value every time the Score is changed on Aha.

Whilst the integration between Aha! and VSO (Visual Studio Online) is a great start, I feel (and have experienced a need) that there can be further collaborative integration between the 2 platforms. My thinking is that it would be great to integra...

It would be great if the assigned to field could be synchronised between VSTS and Aha features and User Stories.

Azure DevOps does not support webhooks on iterations which means that updates to fields on linked Iterations will not flow from DevOps to Aha! However when specifying the Iteration field mappings in the DevOps integration in Aha!, it is possible t...

VSO does not have a good handle on representing releases. Can't really use the iteration mechanism, if your team is working on overlapping releases. Currently I'm using a highest level Feature in VSO to represent a release (or the Backlog) and the...