Follow work across many repositories

Products rarely live in one repository. Virtual projects pull several boards into one view without moving any issues.

The problem

A product spans an app, a service, a website and a few libraries, each with its own repository. Planning across them means opening several boards, or giving up and keeping a spreadsheet.

How Kanbus helps

A virtual project lists other Kanbus projects by path. The console and the CLI read them together, so one board shows every repository's issues side by side, labeled by project, while each issue stays in the repository it belongs to.

What you set up

Local files in each repository, each with its own project key.
A virtual_projects entry in the umbrella project's .kanbus.yml that points at the other checkouts.

Read about virtual projects