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 suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365759/allow-users-with-a-visual-studio-professional-lice.html Users with Visual Studio Professional licenses are able to use source control. However, they are not allowed to access any packages stored in VSTS Package Management. In order to do development, they need to be able to access the packages stored in Package Management. This requires all developers to have a VS Enterprise license or an additional license for Package Management needs to be purchased for all of our developers. This licensing model doesn't make sense. Please fix the license model or we will use an alternate solution.

This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365759/allow-users-with-a-visual-studio-professional-lice.html Users with Visual Studio Professional licenses are able to use source control. However, they are not allowed to access any packages stored in VSTS Package Management. In order to do development, they need to be able to access the packages stored in Package Management. This requires all developers to have a VS Enterprise license or an additional license for Package Management needs to be purchased for all of our developers. This licensing model doesn't make sense. Please fix the license model or we…

Wow, this was great feedback and real quick too. Repo level wiki is something that we will be releasing in the next 2 sprints (fingers crossed). I will update this thread. If I forget then please check my blogs on aka.ms/devopswiki or tweets @sandeepchads. I will be making some noise there for sure :)

This is what I will do after we release the repo level wiki. I will close this feedback item and reopen another one for only team level wiki so that I can free up your user votes. Also, that will help me understand the real need for team level wikis. Hope you are all fine with it.

This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365432/assign-code-review-to-a-tfs-group.html In any medium to large development environments that I know, each team has at least a few senior developers that do code review on a regular basis. We also fall in this category and we could really use a way to assign code review to a TFS Group, instead of adding each one of the code reviewers in the team to every code review request

We have a lot of investment taking place on our code review platform, including group assignment. Adding this for TFVC is still on our backlog, but it is not in our 6 month plan, so we are resetting the status.

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.

Status: I have New, Active, Closed. I'd like to have the sort order match the chronology of the workflow, but all I can get is alphabetical.

Stack Rank: We use stack rank to organize the most pressing work item, but don't apply it to all items in our backlog. However, when i sort on this field ascending items that don’t have any rank at all are always put first. I need them on the bottom.

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.

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.

- In enterprise customers, their current data security policies does not consider the cloud environment yet. Currently, they are trying to change their own security policies, but it also takes very long time and big effort. And if they want to use the cloud environment (such like VSTS) now, they require the exception approvals in their company. But it also takes long time and effort.

- The localization of VSTS is not a strong adoption blocker in Japan. Because even if the VSTS is not localized, the Visual Studio is already localized. Many developers mainly use Visual Studio for their daily work. In addition to this, although the developers have to use some tools only in VSTS (such like WIT), but they can use Japanese language for data entry.

- In enterprise customers, their current data security policies does not consider the cloud environment yet. Currently, they are trying to change their own security policies, but it also takes very long time and big effort. And if they want to use the cloud environment (such like VSTS) now, they require the exception…

When using the On-premises XML process model:
1. Valid transitions can be defined. For example, State A to B is allowed, but state A to C is not allowed.
2. Transitions can be restricted to specific users. For example, State A to B is only allowed to members of group 'Approvers'.

When using the Inheritance process model in VSTS:
You can define a custom rule. However, these do not support State fields.
1. Valid transitions can be defined. But you cannot configure valid state transitions.
However: "You can't specify allowed transitions, all transitions are defined from any state to another state (except to the Removed state)."
Source: https://docs.microsoft.com/en-us/vsts/work/customize/process/customize-process-workflow2. Since no transitions can be defined, no security can be applied.

The wish is that 1. and 2. would be supported in the inheritance process model.

When using the On-premises XML process model:
1. Valid transitions can be defined. For example, State A to B is allowed, but state A to C is not allowed.
2. Transitions can be restricted to specific users. For example, State A to B is only allowed to members of group 'Approvers'.

When using the Inheritance process model in VSTS:
You can define a custom rule. However, these do not…

This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365380/make-workitem-templates-first-class-citizens.html It should allow creating workitems based on templates (which have pre-filled data). Creating hierarchy of workitems based on template(s). e.g. creating a template for Product Backlog item such that it would include the standard tasks (Sprint Backlog Tasks), Acceptance Tests in them (like Code Review, Writing Test Cases, etc). Organizing those tempales in folders. Some of this exists already, but the main missing piece is that you would have linked templates that would also be applied.

This feature will allow you to create a Dashboard that has no association with the team. This means you don’t need to create a team, to make a Dashboard. You can create any number of these Dashboards and share them with who you want.

As part of this feature you will also be able to create personal dashboards that only you can view/edit.

This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365509/enable-editing-board-column-and-board-lane-work-it.html When you add columns to a the Kanban boards you have to map them to a Work Item State. When you add columns to the board you soon run into a case where multiple columns get mapped to the Work Item state unless you edit the Work Item Type Definition and add custom States to work item and then map the Kanban column to the newly added State(s) . It would be nice to be able to update the Kanban board columns and as a bonus swim lane when editing the work item. While the Board Column and Board Lanes were added as fields in TFS 2015 Update 1 they appear to be Read Only. It would be nice if these were editable so whether you are using Kanban board to drag/drop work item or editing Work Item Directly you can have similar functionality to manage the Kanban Column and Lane.

This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365509/enable-editing-board-column-and-board-lane-work-it.html When you add columns to a the Kanban boards you have to map them to a Work Item State. When you add columns to the board you soon run into a case where multiple columns get mapped to the Work Item state unless you edit the Work Item Type Definition and add custom States to work item and then map the Kanban column to the newly added State(s) . It would be nice to be able to update the Kanban board columns and…