Struggling to scale to 2 development teams

Zenhub Product Q&A
1

I have 2 repositories (repo A and repo B) with a large number of existing issues which are github issues.

We’ve currently been one team with one Workspace.

We are splitting our development team into 2 development such that team 1 works on most of the issues in repo A and no issues from Repo B, while team 2 works on a smaller number of issues in repo A, and all issues in repo b.

I tried to go for a 2 workspace option but it’s not looking great - my problem is that for Team 2, we have to add both repo’s A and B, but this means the new issues pipeline is filling up with irrelevant issues for Team 2. It seems in each workspace I could have a pipeline for “Other Team”, but it seems really annoying to groom the issues multiple times into these pipelines. A big concern also is both workspaces having an issue go into this column and then its “lost”.

Using labels and filters doesn’t work either because I don’t want to label everything in repo 2 - the filter would need to be a specific label, only for repo 1, and I would want that then workspace wide by default which isn’t possible.

A single workspace isn’t create either for the same thing as above - a view with the team 2 label would then need every issue in repo 2 to have this same label.

Using zendesk issues works as it can be workspace specific and moved between workspaces, but we’d have to convert all our issues to zendesk issues (idk if this is even possible - I know I can go from zendesk issue to github but not the other way around). Plus we can’t attach the PRs to zendesk issue the way wen can with github issues so this solution also seems bad.

Struggling here and looking for help!

2

Hi,

I would want that then workspace wide by default which isn’t possible.

We actually have a solution in the app today to help with situations just like this. It’s called “Filtered Workspaces”.

Here’s a youtube video that covers how to set it up.

You could build a workspace that includes both repos, and then filters out everything without your team label. It’s a one-time setup, then once you and your taem are working in your filtered workspace, every issue will automatically get the label for you and your team. Give it a try…

Hope this helps,
George

(note: the video is a few years old, a few things have moved around in the app, but that setting is in the same place)

3

Thanks, I will give that a shot and report back!

4

This solution is problematic in that because team 2 only works in repo B, so now every issue in repo B would always have the team 2 label which is both annoying, and risky for missing issues if any miss the label.

If the workspaces had this option on at repo level under “Workspace issue sources”, so I could configured this just for repo A for team 2 that would work perfect.