How do I organize project boards for a multi-repo initiative?

[Suhebdevtechnosys]

If my work is spread across multiple GitHub repositories, how should I set up my project board so everything is organized in one place?

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[pankajkumarsha]

Why is my project not getting uploaded, I have decided it many times..

[CalderMatt09]

A good starting point is creating an organisation-level project board instead of tying the board to a single repository. That allows you to pull issues and PRs from any repo into the same workflow. Using fields such as status, priority, and component can help categorise work across repositories without losing context.

Another helpful practice is to standardise labels and naming conventions across repositories. When labels like feature, bug, backend, or frontend are consistent, filtering and grouping items in the project board becomes much easier. Teams can also link related issues across repos so that dependencies are visible from the same project view.

For larger initiatives, it also helps to separate planning from execution. The project board can track initiative-level tasks, milestones, and progress while the detailed implementation work remains in each repository. Pairing this with structured QA tracking using software test management tools like Tuskr can give teams a clearer view of both development progress and validation across the entire multi-repo effort.

[Binary-ShadowMonarch]

Use GitHub Projects (Projects v2). It’s built for multi-repo work.

Create a project at the org (or user) level, then add issues/PRs from any repo into one board. Group by status, add a simple Repo or Priority field, and filter using shared labels. That’s usually enough to keep a multi-repo initiative clean and visible.

If you want less manual work, enable automations (auto-add by label, auto-move on merge). No extra tools needed unless things get really big.

Helpful refs:

Docs (straight from GitHub):
https://docs.github.com/en/issues/planning-and-tracking-with-projects
GitHub Project Management Tutorial // Managing Issues Across Multiple Project Boards
https://youtu.be/wj_4KV3r1GI

[Giorno-Giovanna-Dio]

A common and clean approach is to use a single organization-level (or personal) project board as the source of truth, rather than tying the board to one specific repository.

You can then:
• Add issues and pull requests from multiple repositories into the same project
• Use custom fields (e.g. repo, area, priority, status) to keep things organized
• Rely on automation (status changes, PR merges, issue closures) to keep the board in sync

In practice, this works well when:
• Each repo owns its code and issues
• The project board focuses on planning, progress, and visibility across repos

This avoids duplication and keeps all work visible in one place without forcing everything into a single repository.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[yesalphahere]

Organizing Project Boards for a Multi-Repo Initiative

---

The Right Structure

Use one GitHub Project (V2) at the initiative level — it can pull issues and PRs from multiple repos into a single board.

Organization Project Board  ←  Repo A issues
                            ←  Repo B issues
                            ←  Repo C issues

---

Step-by-Step Setup

1. Create an Org-Level Project

Organization → Projects → New Project → Board or Roadmap view

2. Add Multiple Repos to It

Project Settings → Linked Repositories → Add each repo

Now issues and PRs from all repos appear in one place.

---

Recommended Views to Set Up

View	Purpose
Board view	Kanban by status (Todo / In Progress / Done)
Roadmap view	Timeline across all repos
Table view	Filter by repo, assignee, or label

Each view is just a different lens on the same data — no duplication.

---

Keep It Organized With These Fields

Add custom fields to every issue:

Repository   → which repo it belongs to
Team         → which team owns it
Priority     → High / Medium / Low
Initiative   → name of the overarching goal

Then group by Repository or filter by Team instantly.

---

Label Strategy Across Repos

Use consistent labels in every repo so filtering works cleanly:

type: feature
type: bugfix
priority: high
team: backend
team: frontend

---

Automation to Reduce Manual Work

In Project Settings → Workflows, enable:

✅ Auto-add items when opened in linked repos
✅ Auto-close items when PR is merged
✅ Auto-move to "In Progress" when PR is opened

This keeps the board accurate without anyone manually updating it.

---

Bottom Line

One Org-level GitHub Project V2 linked to all your repos is the correct approach — not separate boards per repo. Use custom fields and views to slice the data however each team needs it.