Managing GitHub issues across multiple organizations

GitHub Projects works well inside a single organization. But if your work spans multiple GitHub orgs or mixes in GitLab repositories, you are stuck context-switching between tabs, boards, and providers.

The problem with GitHub Projects

GitHub Projects is scoped to a single organization. If you contribute to repositories across two or three GitHub organizations, or if some of your work lives in GitLab, you cannot see all your issues on one board. Each organization gets its own project with its own views and backlog. There is no way to combine them.

If you work at a company with multiple GitHub orgs, you already know the routine: open one project to check on client A, switch to another for client B, then open GitLab for the internal tooling repo. Your actual workload is scattered across browser tabs.

Open-source maintainers with a day job run into the same wall. So do freelancers with multiple clients.

Common workarounds and their limits

There are a few ways people try to deal with this. None of them really work.

  • You can create a separate GitHub Project for each organization, but then you are managing multiple boards with no cross-board view.
  • Some teams track issues in a shared spreadsheet. This works until someone forgets to update it, which usually takes about a day.
  • Tools like Jira, Linear, or Shortcut can aggregate work, but they often require importing issues into their own system. You end up with two sources of truth.

How Overvy solves this

Overvy is an issue board that works across providers. You connect your GitHub accounts and GitLab instances, and Overvy pulls all your issues into a single kanban board. It doesn't care how many GitHub organizations you belong to or whether some repositories are on GitLab.

  • GitHub and GitLab issues sit side by side on one board. Drag them across lanes, triage your backlog, and plan your week without twelve open tabs.
  • Changes sync both ways. Move an issue to Done on your Overvy board and it closes on GitHub. Reopen it and it reopens on GitHub. It is a live view, not a copy.
  • Overvy uses GitHub App installations and GitLab personal access tokens. You choose exactly which repositories to connect. No code access, ever.
  • Workspaces let you group issues by client, team, or context. Switch between them without losing your board layout.
Early Access

One board for all your organizations

Overvy is built for developers who work across multiple GitHub organizations and GitLab instances. Join the waitlist to get early access.