156 votesunder review · 18 comments · Azure DevOps (formerly Visual Studio Team Services) » Test Plans · Flag idea as inappropriate… · Admin →Richard Zaat commented
Is there an ETA on this? In our organization we really need this to enable testers to move away from their current toolset. With test it is very important to understand what has been tested. Weird that in this case the test artifacts are work items themselves, but the standard link type is not used to relate them.
426 votes32 comments · Azure DevOps (formerly Visual Studio Team Services) » Version Control (Git/TFVC) · Flag idea as inappropriate… · Admin →Richard Zaat commented
I agree, we currently have >150 GIT repositories in our project, and it is becoming a real pain. Everything else in Azure DevOps can be grouped in some way or the other, except GIT repos. And all I am asking for is a security folder structure, same as with the build definitions for example. So I can have groups of people taking care of their own GIT repos, instead of them needing a project admin to create a new one.