Allow to filter Azure DevOps repos in workspaces

40 votes

I'm working on a project with multiple teams, and about 100 repos.
I know it is a bit extreme but I don't need everything in my workspace. And especially not in my pull request view.

Done Suggested by: Martin (20 May, '22) • Upvoted: 10 May, '23 • Comments: 16

Comments: 16

09 Jun, '22
Kyle Korndoerfer
As an Azure DevOps user, I would like to be able to filter the repos display in a workspace after selecting my DevOps Project instead of seeing all of the repos so that I can see just the repos that are of importance to me.

I Just created a personal workspace for the first time linked to my Azure DevOps instance and noticed that there is no way to filter the list of repos under the team project to only the repos that I am interested in (like you can do with GitHub).

The Azure DevOps Project I am connected to contains many microservices each in their own repo, but I only care about a select portion of them. It would be awesome if I could filter out the repos that I don't care about instead of having to scroll through a long list of ALL of them to find the ones I am interested in. In addition, it makes it hard to quickly look at the list and see the state of all of the repos that I care about.
23 Jun, '22
Jeremy Ramsey
We have a similar scenario, and I would love the ability to manually add which repositories are in my workspace instead of the workspace automatically importing all (up to 100) repositories that the project contains.
11 Jul, '22
Daniele Magliocchetti
Same issue here, we have more than 100 repos in our project and it would be nice to create different workspaces with just a subset of them.
If this is not possible, the number of repos in a workspace should be increased.
21 Sep, '22
Joey Kelroy Admin
"Create workspace from subset of Azure Devops repositories" (suggested by Alun on 2022-09-14), including upvotes (1) and comments (0), was merged into this suggestion.
24 Oct, '22
Niklas Arens
We have the exact same problem with over 100 repositories in one project. This feature is vital for workspaces to be usefull to us.
26 Nov, '22
Keith Ebbitt
I'm having the same issue. There are hundreds of repo in the ADO project I'm connecting to and none of the 100 that have been brought in are among the ones I use. This would be essential for me to make use of workspaces.
14 Dec, '22
Vincent Prince
+ 1 for this issue. With the GitKraken 9.0, local workspace helps a bit (I can select my subset of repository from my huge ADO project). But then when converting to a cloud workspace, we're back to square 1 and it's listing all repos.
08 Feb, '23
Tim Lewis
Oh yes please. Github.com integration allows for it. I can't see why ADO wouldn't. Cloud Workspaces are amazing, please make them usable for large companies on ADO.
Click to enlarge

08 Feb, '23
Casey Merged
I work in an Azure DevOps organization with many projects, each with thousands of repositories (Microsoft). I can only see 100 repositories in the list and none of which are the ones I work with. When I type in the name of my desired repo in the search bar, it only filters the current 100 and does not query the server again for new results.
08 Feb, '23
Joey Kelroy Admin
"Remove Limit of 100 Repositories in Workspaces or Allow Server-Side Search" (suggested by Casey on 2023-02-08), including upvotes (1) and comments (0), was merged into this suggestion.
10 Feb, '23
Jon Taylor
This is a much needed feature for large organizations. GitKraken workspaces is not a useable feature when used with ADO and more than 100 repositories.
05 Apr, '23
Chad
Rather than have to manage this repo by repo, workspace by workspace; I would think this is something that should really be done by creating a link between the GitKraken Team and the Azure DevOps Team. Within a single DevOps Project, we have many groups of repos, and permissions are setup by Azure DevOps Teams. Being able to tie a DevOps Team(s) to a GitKraken Team would allow management at a group level instead of having to manage it on each individual item.
05 Apr, '23
Chad
For what it's worth, DevOps' recommended configuration is to create a single Project with multiple Teams within it, and only add more Projects if needed(links below). At the very least, GitKraken Workspaces should be able to be configured so the scope of what is retrieved from Azure DevOps for the visible Workspace is first by DevOps Project, and optionally by DevOps Team. I can also see it making more sense to be able to link a GitKraken Team to an Azure DevOps Team, so the respective work items and repos for a DevOps Team will follow through to the GitKraken Team.

Sources:
- https://learn.microsoft.com/en-us/azure/devops/organizations/projects/about-projects?view=azure-devops#use-a-single-project
- https://learn.microsoft.com/en-us/azure/devops/user-guide/plan-your-azure-devops-org-structure?view=azure-devops#single-project
08 May, '23
Trevor Admin
You can now add specific Azure DevOps repos to a Cloud Workspace from any Azure DevOps project with the release of GitKraken Client 9.4!

Please visit our release notes for more details: https://help.gitkraken.com/gitkraken-client/current/#version-9-4-0

Thank you for providing feedback to help improve GitKraken Client!
09 May, '23
Chad
This is not yet "Done". This configuration is not accessible when editing a Workspace, only when creating. Even if I go through and recreate all GK Workspaces today, I won't be able to add a Git repo we create next week to the workspace. To be truly marked as "Done", we need this accessible when both Creating and Editing.
10 May, '23
Joey Kelroy
Hi Chad, I agree that this functionality would be useful and I have created a new feature request to support this here: https://feedback.gitkraken.com/suggestions/445101/ability-to-manually-select-repositories-for-existing-azure-workspaces.