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 site is for feature suggestions; if you need to file a bug, you can visit our Developer Community website to get started.
Note: your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy and license terms.
We look forward to hearing from you!
- The VSTS Team
- Visual Studio (UserVoice)
- Visual Studio for Mac (UserVoice)
- Visual Studio Code (GitHub)
- Azure Application Insights (UserVoice)
- Visual Studio Documentation (UserVoice)
- TypeScript (GitHub)
- NuGet (GitHub)
- Windows APIs and developer features (UserVoice)
- Microsoft Edge (UserVoice)
- MSBuild (GitHub)
- Xamarin (UserVoice)
-
Implement AD FS for TFS
This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365455/implement-ad-fs-for-tfs.html
Our organisation policy does not allow us to use TFS Online / visualstudio.com. For on-premises TFS instances, ADFS is not supported at the moment. I'm hoping a future update will incorporate the ADFS bits for TFS Online in the on-prem version as well. That would open up some authentication schemes we'd like to use.207 votes -
better permission management (user interface, identity picker)
This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365834/better-permission-management-user-interface-identi.html
Permissions can be assigned at project level. This works very well. A user can see only the project in which he is involved.
But the user can access the User Page and can see all the other users oft the VSTS account.
Also every user can select all other users from the Azure AD in the identity picker of a WorkItem (no matter if the user is in the same project or not).
A customer user should not know our other customers. Also…152 votes -
Visualize the rights of a user/group on all different aspects of a Team Project
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.131 votes -
FIPS
This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365471/fips.html
Use FIPS compliant algorithms if FIPS policy enforcement is enabled on the server. Department of Defense Security Technical Implementation Guides require that FIPS policy is enforced: http://www.stigviewer.com/stig/microsoft_dot_net_framework_4.0/2014-01-08/finding/V-30926This applies to all US Department of Defense. It is understood that MD5 is much faster and might not even be used for security reasons (i.e. using MD5 to generate a hash to determine file differences on version control check in). However if FIPS is enabled, why not use a FIPS compliant algorithm?
It is much…
57 votes -
Make Service Hook Permissions more flexible
This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365713/make-service-hook-permissions-more-flexible.html
service hookAllow a permission level to assign users to be able to modify the service hooks. We often have user's who currently do not have permission level high enough to edit the service hooks for the project, nor do we want to give them the permission level that is that high. We would like to be able to assign the ability to modify service hooks to users at a lower permission level. Currently there is no permission level we can just toggle…
47 votes -
Team level access
This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365524/team-level-access.html
Multiple teams can be configured in a project. Allow users to be restricted to teams, limiting access to the other teams and their areas.
Members can already be specified per team, but users can still see and access other teams on the same project.A lot of experts suggest using one project due to the inter-decencies between work and code and therefore we and a lot of development teams use one project.
Allowing stakeholders to only access one specific teams are very important.…
47 votes -
Separate Test Suite Permissions - I would like to see Modify and Delete as separate permissions in TFS
This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365542/separate-test-suite-permissions-i-would-like-to-se.html
with TFS update 3 Test Suite permissions were added which is a good step in the right direction. I would like to see a step further. Separate the Create, Read, Update and Delete Permissions. In my situation i want Feature owners in QA to be able to create their own test suites and add or modify tests, but i do not want them to be able to delete. The deleting of suites or tests within suites needs to be reserved to management. I…45 votes -
Support for Active Directory Group Managed Service Accounts.
This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365494/support-for-active-directory-group-managed-service.html
I don't know how we have gotten TFS 2015 to RTM without including support for Active Directory gMSA (Group Managed Service Accounts) for the basic installation and operation of the services associated with TFS. The gMSA concept has been well accepted for awhile now and most other MS software that TFS relies on can leverage them (SQL Server, IIS, etc). So why hasn't support for them been added to TFS?!?43 votes -
Reset code reviewer votes when there are new changes has bad side effects
This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365806/reset-code-reviewer-votes-when-there-are-new-chang.html
If the branch policy "Reset code reviewer votes when there are new changes." is set on a branch when a user pushes more changes all code reviewers are reset. The goal here is to not allow unreviewed changes to sneak in with previously review changes.However, this also has the side effect of resetting users who are blocking the review in a waiting state. For instance, I may have some issue with a code review, so I set my state to waiting. More…
39 votes -
Set branch security by REST API
This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365711/set-branch-security-by-rest-api.html
For git branch security, we can set access control (such as set force push as deny) manually by selecting a git branch, and clicking Branch security. It will be better if we can set branch security by REST API.36 votes -
Allow testers with Manage Test Artifacts Permission to be able to delete test artifacts again
This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365776/allow-testers-with-manage-test-artifacts-permissio.html
In previous versions of TFS, "Manage Test Artifacts" allowed a user to delete test artifacts. Please PUT THAT BACK. Now to delete test artifacts you need to give them Permanently delete work items, which lets them delete way to many artifacts.26 votes -
Ability to link VSTS to Multiple Azure Active Directory instances for Vendor Collaboration
This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365891/ability-to-link-vsts-to-multiple-azure-active-dire.html
Due to changes made by Microsoft no longer allowing creation of a 'personal/live account' with a custom domain this has impacted any 3rd party suppliers ability to smoothly assist customers on their projects in VSTS.For VSTS instances from April onward all account used for authentication must be either an official live account (live.com/outlook.co.uk) or a business account which is contained with the Azure Active Directory instance it has been paired with.
The issue is that all VSTS instances for client security ultimately…
23 votes -
Allow more permission management on stakeholders
This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365611/allow-more-permission-management-on-stakeholders.html
I would like to be able to manage what stakeholders can and cannot view/access with a higher granularity.
Specifically, I would like to be able to block a stakeholder from accessing the "Users" area or, at least, don't let them see other users who do not belong to the same projects as them.23 votes -
Avoid that users can see all other users in VSTS
This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365641/avoid-that-users-can-see-all-other-users-in-vsts.html
If we invite a client as stakeholder, he can see all users with their email addresses,
So that could be competitors.
We don't want our customers to see what other customers we work for. Some might be restricted/private.22 votes -
LiveID aliases
When one user authorizes another to their TFS or VSO project, they do so by email address. But if the address they specify is a secondary alias on my LiveID, the authorization does not work. It only works if the address is my primary Alias. If the alias is "confirmed" through my LiveID (msAccount), then authorization should work.
22 votes -
Allow users to choose which Live ID Service account they want to use. I signed up and it took the wrong one!
TFS online signup seems to just grab the first live ID it finds. I actually wanted to sign up with a different one!
18 votesAs 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.
Ewald Hofman
-
field level security permissions
This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365854/field-level-security-permissions-1.html
Ability to lock field with limited access to some users / groups.17 votes -
Add notification for expiring Personal Access Tokens
There needs to be a notification sent to all admins (or possibly a selected user) when a Personal Access Token is about to expire. Maybe give a 2 week notice.
Use Case:
I have been working at my company for about a year and all of a sudden our builds and other automated code stopped running and there was no notice and no good error messages besides authentication failed. It turns out the previous person just added a token and it expired after a year without anyone knowing where to look since he no longer works here.
16 votes -
Identity control must take valid values into account
The new Identity control in TFS 2015 makes use of MRU list and a Search option. However, that allows to select identities which are not allowed. You may select e.g. users who have left (so no roles any more, only present in Valid Users list), or users in same collection but not present in current project.
Only after selection the feedback (by yellow background) is given.This happens on the work item dialogs. Direct editing on the boards still supply the possible/valid users to select from.
15 votes -
Extend Read Only TFS Users to read/edit all work items (or sell new type of CAL)
Hi,
This is more of a request than a question. Our developers are using TFS (all have MSDN), but in order for the whole company to adopt TFS we need other departments such as customer support and QA to be able to view, create and edit Work Items.
At the moment you only allow non-TFS users to create new items and view only items they have created. This is extremely limiting and means that we need a massive number of CALS for TFS which cost $499 each. It is a crazy cost for a user only accessing work items. These…
14 votes