Azure DevOps (formerly Visual Studio Team Services)

Announcement: This forum has been migrated to provide you one convenient and responsive system for all feedback. You can now suggest new ideas, browse and vote on existing ideas in the Azure DevOps Developer Community. To learn more about the migration please check out the release blog post

We’d like your suggestions and ideas to help us continuously improve future releases of Azure DevOps and Team Foundation Server (TFS), so we’ve partnered with UserVoice, a third-party service, to collect your feedback. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.

This is a great idea! I want to let you know that we have included your suggestion in our next 6-month plan. We will check back as soon as possible with any updates to this request.
Shashank Bansal
Program Manager

It would be great to have access to the reporting capabilities in the Warehouse and the Cube to enhance the analysis capabilities with VSO. Especially around testing and other such capabilities we would really benefit from having some degree of reporting access (even if it was just against SQL Azure and didn't provide cube access)

This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365387/visualize-the-rights-of-a-usergroup-on-all-differe.html You can set rights in TFS on a lot of different levels. On Team Project, Area/ Iteration/ Team Queries, Source Control/ Folders/ Files, Builds / Reports / SharePoint. Especially in TFS with different TFS groups that sometimes contain the same users/groups, it is hard to see why a user has a specific right or is not allowed to do something. At the moment it is hard to find this without checking everything manually.

This is a great idea! I want to let you know that we have included your suggestion in our next 6-month plan.
We will check back as soon as possible with any updates to this request.
In the meantime, please share specific reports that you may want to have available out of the box with us.
Shashank Bansal
Program Manager

It would be great to be able to trigger a Rollback activity if the release is Rejected by some of the Approvers.

By now, when it happens, we need to trigger a new Release manually to rollback the application to the previous version. It takes a hard work because we need to find the latest valid (and released) build, etc.

This is a great idea! I want to let you know that we have included your suggestion in our next 6-month plan. We will check back as soon as possible with any updates to this request.
Shashank Bansal
Program Manager

As explained in this blog post (http://blogs.msdn.com/b/visualstudioalm/archive/2015/10/08/how-we-use-user-voice-to-make-a-better-product.aspx), we had updated the status of this suggestion to “Under Review” to let you know we are tracking it on our backlog. To better indicate which one we are actively working on or which ones are on our 6-month plan, we introduced the states “Started” and “Planned”. The goal is to give an update on in progress suggestions at least every 3 months. This suggestion is still on our backlog, but they are not part of the 6-month plan.

This is a great idea! I want to let you know that we have included your suggestion in our next 6-month plan. We will check back as soon as possible with any updates to this request.
Shashank Bansal
Program Manager

We’re starting to take a look at this feature, and have some questions about exactly what people are expecting from this suggestion.

Currently, the pull-request diff experiences ignore leading and trailing whitespace by default. For example, if only the indentation of a line changed, that line will not be highlighted as having any changes. This leads us to believe that this suggestion is about some other whitespace diffing behavior.

We have some ideas about what this might mean, but we want to hear from our users. If you have any insights you wish to share to help us better understand this suggestion, please reply to this email and let us know.

Here is the scenario: I get an email from someone in the company with a bug or feature request. They don't normally use VSTS/TFS (i.e. a stakeholder). I create the work item on their behalf. They are not members of the project, but I want them to be updated as the work item changes. I would like to add that person or person to the list of Followers for that work item.

If that person does not currently have a TFS license, they should be assigned a Stakeholder license.

Here is the scenario: I get an email from someone in the company with a bug or feature request. They don't normally use VSTS/TFS (i.e. a stakeholder). I create the work item on their behalf. They are not members of the project, but I want them to be updated as the work item changes. I would like to add that person or person to…