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.

With the links, I could create a query to list all test cases in a specified test plan. In Test hub or MTM I can export such list to email or print to PDF, but there is no way to get it in Excel format, which would I get for free if I could query.

With the links, I could create a query to list all test cases in a specified test plan. In Test hub or MTM I can export such list to email or print to PDF, but there is no way to get it in Excel format, which would I…

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.

Then add a "fork" button next to the "clone" link that would automatically clone in a new repo in "My Repositories" Git folder. Repositories here should still have their origin remote and be available to submit Pull Requests against the origin.

This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/366004/bring-back-tree-view-to-queries.html Bring back the query left pane. The new query experience "streamlines" the queries by removing left pane and forcing you to favorite queries for easier access. What I previously accomplished in one click I now I have to perform multiple clicks and type into a filter. This is the opposite of streamlining.

We are currently exploring ways we can improve the navigation experience of Queries based on all the feedback we have received. Several User Voice tickets have been merged so that we can consolidate your comments and provide a single channel for communication.

This suggestion remains under review. Like we often do in VSTS engineering, we are in process of building integrated tooling for Microsoft’s engineering teams to enhance the sophistication of our own processes for governing OSS usage and managing risk. We are continuing to assess how this meets the needs of external customers as well as aligns with our commercial priorities and will provide updates should we decide to turn what we use internally into a public offering for our customers. The VSTS marketplace does include offerings from partners that integrate well with VSTS to provide Component Governance services.

For the next 6 months, we won’t be taking new package formats, as we’re finishing Maven and planning major improvements to our existing NuGet and npm support and new features to improve the package lifecycle, like Package CI and Package CD for better Team Build and RM integration.

However, we’re very interested in your input to define the next wave of package formats that are supported by Package Management so that we can inform our next major planning wave. So, we’ve left all “Ecosystem”-tagged requests open for voting.

1) Does my application support *** users?
2) If not, what do I have to do?

We could create a guide teaching how to combine Cloud Load Test, Application Insights and Windows Azure in order to show how to answer these questions.
• What scenarios should I consider for my Load Test?
• How many agents do I need? How to know if the agents are over capacity?
• How to distribute the user load?
• All my requests returned HTTP 200. Is it good? Cache / CDN could help me on this topic?
• What Performance Counters should I evaluate?
• How to identity issues using App Insights?
• I have a lot of users in my IIS Queue. What does it mean?
• I have requests taking more than 2 minutes. How to identify the bottleneck?
• How to setup Windows Azure to scale automatically in order to support my load test?
• Etc …

I would like to provide a guide to answer two simple questions:

1) Does my application support *** users?
2) If not, what do I have to do?

We could create a guide teaching how to combine Cloud Load Test, Application Insights and Windows Azure in order to show how to answer these questions.
• What scenarios should I consider for my Load Test?
• How many agents do I need? How to know if the agents are over capacity?
• How to distribute the user load?
• All my requests returned HTTP 200. Is it good? Cache / CDN…

Looking ahead to the next 6 months, we’re committed to other investments, including finalizing upstream sources and starting on package metrics (currently our top suggestion); so, we don’t expect to start on another package type between now and summer. However, all package type/protocol suggestions remain open and we appreciate your continued votes.
Alex Mullans
Program Manager, VSTS

Looking ahead to the next 6 months, we’re committed to other investments, including finalizing upstream sources and starting on package metrics (currently our top suggestion); so, we don’t expect to start on another package type between now and summer. However, all package type/protocol suggestions remain open and we appreciate your continued votes.

Looking ahead to the next 6 months, we’re committed to other investments, including finalizing upstream sources and starting on package metrics (currently our top suggestion); so, we don’t expect to start on another package type between now and summer. However, all package type/protocol suggestions remain open and we appreciate your continued votes.
Alex Mullans
Program Manager, VSTS

Recently we had to explore ideas how to share our binaries from VSTS. As it's not a problem for source files to use :git notation with VSTS repository, it becomes an issue when you have to share compiled binaries. This can be approached by droping binaries to artifactory, linking to the URL with :http notation inside Podfile and specifing PAT in .netrc file (:http uses curl to fetch package). Still, this solution is not ideal and would be great to have Cocoapods packaging in place.

Looking ahead to the next 6 months, we’re committed to other investments, including finalizing upstream sources and starting on package metrics (currently our top suggestion); so, we don’t expect to start on another package type between now and summer. However, all package type/protocol suggestions remain open and we appreciate your continued votes.
Alex Mullans
Program Manager, VSTS

capacity planning by tasks assigned to the current sprint works well (but only when there are tasks). When looking forward to schedule the next sprint/iteration, we would like to use the capacity planning tool in the backlog to reflect capacity based upon the estimated effort of the user stories / PBIs. When tasks are eventually added, then the story/PBI's effort is ignored and the child task remaining effort is used towards the capacity. This can help teams plan a sprint at a high level by assigning un-tasked stories/PBIs.

Example: Assume Sprint 1 has no stories/PBIs assigned, and the team's capacity is 10. 10 PBIs exist, each with an effort of "2". No tasks have been created for the PBIs. On the sprint 1 backlog screen, as I assign PBIs to the sprint, I would like to see the capacity affected when a PBI is assigned (even though it has no tasks), i.e., when I assumed the first PBI (with effort of 2) to the sprint backlog, it show I have 8 for a remaining capacity. After assigning the second PBI, I have 6 remaining capacity.

When I start to task out my Sprint backlog, then the estimated task hours remaining will override the PBI effort estimate. For example, assume there are 5 PBIs in the sprint backlog, each with 2 effort, and the team's capacity is 10. The team is currently at capacity. Now assume we add a single task to a PBI with an effort of 6 hours. This will override the parent PBI's effort of "2" and show that we have an estimated level of effort of 14. Because we have provided a more realistic estimate in a task, it affects our plan and suggests we should remove several other un-tasked PBIs to stay within capacity.

Other thoughts: this assumes story/PBI "effort" is actually hours, which is technically a no-no in big "A" Agile world. So perhaps there should be 2 different capacities: story/PBI effort capacity and task capacity. We already have task capacity, so leave that "as-is", but for planning purposes, add a "planning capacity" that can be entered in a similar manner (or just a single number) that we can target for the sprint/iteration. At an early sprint planning phase this planning capacity can help you establish a target for the un-tasked stories/PBIs you add to the sprint.

capacity planning by tasks assigned to the current sprint works well (but only when there are tasks). When looking forward to schedule the next sprint/iteration, we would like to use the capacity planning tool in the backlog to reflect capacity based upon the estimated effort of the user stories / PBIs. When tasks are eventually added, then the story/PBI's effort is ignored and the child task remaining effort is used towards the capacity. This can help teams plan a sprint at a high level by assigning un-tasked stories/PBIs.

Example: Assume Sprint 1 has no stories/PBIs assigned, and the team's capacity…