Skip to Main Content
ADD A NEW IDEA

Azure DevOps Services and Server

Showing 5

TFS Integration, match user for "assigned to" field

Aha! takes my email address as user name but TFS requires <DOMAIN>\<Last Name> as user name. Therefore the integration throws errors when an Aha! user is set in the TFS "Assigned to" field of a feature. My suggestion to solve this is t...
Guest over 6 years ago in Azure DevOps Services and Server 3 Unlikely to implement

Automate service account password updates for TFS integrations

Right now we have a TFS integration configured with Aha which requires us to use an AD service account for TFS. This service account password needs to be manually added within Aha! however we have a policy that all our service accounts require pas...
Jeremy Lawson over 6 years ago in Azure DevOps Services and Server 0 Unlikely to implement

Would it be possible to not need a paid AHA account to process VSTS updates?

At the moment we have set up the VSTS integration with a paid AHA account as required. This means that all updates come in from that product manager. In the history threads, and the notification emails we get a combination of VSTS updates, and the...
Guest almost 8 years ago in Azure DevOps Services and Server 1 Unlikely to implement

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 about 8 years ago in Azure DevOps Services and Server 1 Unlikely to implement

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 almost 9 years ago in Azure DevOps Services and Server 1 Unlikely to implement