ADD A NEW IDEA

My votes: Azure DevOps Services and Server

Showing 90

Properly transfer images in VSTS comments to Aha!

Currently, if a user adds a comment to a User Story or Bug discussion in VSTS and embeds an image in the comment, the image doesn't come through with the comment that shows up in Aha!. This makes it difficult for the reader in Aha! to follow the d...
Guest almost 6 years ago in Azure DevOps Services and Server 0 Future consideration

Fix critical Aha to VSTS Integration not syncing Feature Order

We are trying sync the Feature order from Aha to VSTS (never the other way around). Keeping the Features in VSTS in the same order in Aha is in our use case, critical to using the integration. The reason that it fails is because matching the Aha R...
Guest almost 6 years ago in Azure DevOps Services and Server 2 Future consideration

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

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 over 6 years ago in Azure DevOps Services and Server 1 Future consideration

Ability to search for key words in Integration updates when importing new records

After the updated TFS integration which allows records to be imported directly from TFS into Aha. It would be ideal to be able to search the new record list for key words. Currently you can filter the list but this is not very user friendly and if...
Guest over 6 years ago in Azure DevOps Services and Server 1 Future consideration

Add ability to transfer requirements between features and features between master features (epics)

If you take the typical hierarchy VSTS, of Epics, Features and Product Backlog items, its is great that with Integrations 2.0 we can map these to Master Features (we call these Epics), Features and Requirements (we call this PBI's). However we are...
Richard Harrison over 6 years 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 8 years ago in Azure DevOps Services and Server 3 Future consideration