Skip to Main Content
ADD A NEW IDEA

Azure DevOps Services and Server

Showing 99

VSTS Integration - Error importing new records into Aha

As we are starting to use more and more Aha!, we are seeing errors while newly created records by Development team in VSTS being imported into Aha!. 2 main reasons for the errors include Feature is not available for the user stories (Requiremen...
Sekhar Nallapaneni over 5 years ago in Azure DevOps Services and Server 1 Already exists

Support acceptance criteria for a requirement, enable sync of acceptance criteria with TFS

each requirement should have an acceptance requirement section that can sync to a user story acceptance criteria in TFS
Guest over 5 years ago in Azure DevOps Services and Server 1 Already exists

Integration by status

I'm not sure how much demand there would be for this, but I've had a need a few times for it so I'm going to suggest it. I would like to be able to limit automatic integration of new requirements if they are in a certain state, such as New. If a f...
Tom Beck over 5 years ago in Azure DevOps Services and Server 0 Future consideration

Sending Sprint to VSTS with complex organization

I can't get my Sprint to land in the right area, it winds up under main as another project instead of sprint under a project when structure is Main>Project>Sprint.
Guest over 5 years ago in Azure DevOps Services and Server 0 Future consideration

Don't fail TFS Integration when attached file is too large

When a file has been uploaded to aha that is larger than the maximum file size,then integrate without the file in TFS, adding a note indicating this. This will allow the team to collborate on the TFS items without having to delete the file.
Guest over 5 years ago in Azure DevOps Services and Server 0 Future consideration

when syncing master features and linked features to VSTS, have relationship between these items persist on the VSTS Side

Here is issue: Create Epic in AHA Create Feature in AHA, linked to Epic above Sent Epic from AHA to VSTS Sending Epic to VSTS does also automatically send the Feature from AHA to VSTS. However, the Epic and Feature in VSTS are not linked.
Brian W almost 6 years ago in Azure DevOps Services and Server 4 Already exists

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

Nested Iteration Paths with VSO / Visual studio team services integration

We have the same VSO project for many products in Aha. We would like the ability to have child iterations for releases so we can group them together in our queries. Current integration only allows us to go 1 level deep in the iteration path. Our...
Josh Wayne almost 6 years ago in Azure DevOps Services and Server 0 Already exists

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

VSTS updating Aha! features base user stories

Leadership and executives are using Aha! more and more. Having the ability to represent the percentage completed of features in a given release is very important when reporting to large audience. I like to ability to show the percentage of the Fe...
Guest almost 6 years ago in Azure DevOps Services and Server 0 Already exists