Cross-project board
Overview
Section titled “Overview”The cross-project board aggregates cards from every project you have access to into one board, organized the same way a single sprint board is, but spanning your whole portfolio. It exists for people who need to see work-in-progress across teams, not just inside one project.
This view is most valuable for multi-project programs where engineering capacity is shared: a PM can see at a glance whether two projects are quietly competing for the same people, something that is invisible from either project board alone.
Cards here are the same underlying task objects you see on individual sprint boards, so status changes made in either place stay in sync automatically. There is no separate cross-project data model to maintain.
What you can do here
Section titled “What you can do here”- See work-in-progress cards across every project you have access to, in one board.
- Filter by project or assignee to focus on a specific slice of the portfolio.
- Drag cards to update status where you have permission.
- Drill into any card for full project-local detail.
- Spot capacity conflicts between projects sharing the same people.
When to use
Section titled “When to use”- Running multi-project programs with shared engineering capacity.
- Weekly portfolio reviews across more than one project.
- Investigating why a specific person appears overloaded across boards.
Prerequisites
Section titled “Prerequisites”- A signed-in member account with access to more than one project.
- A Planner seat to move cards; Viewer seats can browse read-only.
Where to find it
Section titled “Where to find it”- Sidebar: Views → Board
- Direct route:
/views/board
Step-by-step
Section titled “Step-by-step”- Open Views → Board (
/views/board). - Filter by project or assignee to narrow the view if the portfolio is large.
- Scan for cards clustering on the same assignee across different projects.
- Drag a card to update its status where permissions allow.
- Drill into a card to see full project-local context when you need more detail.
- Cross-reference with a capacity view before promising a new commitment across projects.
What success looks like
Section titled “What success looks like”- You can see the state of work across projects without opening each one individually.
- Capacity conflicts between projects surface before they cause a missed sprint goal.
- Status changes made here reflect correctly back on each project sprint board.
Tips & best practices
Section titled “Tips & best practices”- Pair this board with a capacity or workload view whenever you suspect two projects are competing for the same people.
- Use filters aggressively; an unfiltered view across many projects gets noisy fast.
- Treat this as a review surface first and an editing surface second.
Common mistakes
Section titled “Common mistakes”- Trying to use the cross-project board as your only working view instead of each project sprint board.
- Missing a capacity conflict because the view was never filtered down to a manageable size.
- Assuming a card moved here is a different object from the one on the project sprint board; it is the same task.