If your system spans multiple repositories (like a frontend UI repo and a backend API repo), you shouldn't have to constantly switch directories to see what needs to be done. Kanbus Virtual Projects allow you to define links to sibling repositories so they all appear as one unified project.

Setup

You can set up virtual projects at the team level via .kanbus.yml, or for your personal local setup using .kanbus.override.yml.

Team Configuration (.kanbus.yml)

Terminal

project_key: app
virtual_projects:
  api:
    path: ../backend-api
  ui:
    path: ../design-system

Personal Overrides (.kanbus.override.yml)

This file should be git-ignored. It additively merges with the main config.

Terminal

virtual_projects:
  my_lib:
    path: ../experimental-lib

Usage

Once your paths are configured, your CLI commands automatically aggregate data.

Terminal

# Lists issues from the primary project AND all virtual projects
kanbus list

# Filter to show ONLY issues from the 'api' virtual project
kanbus list --project api

# You can combine project filters with standard filters
kanbus list --status open --project api

Note: Paths are relative to the repository root. Virtual project labels cannot match your main project_key. If a path is missing or invalid, Kanbus will fail with a clear descriptive error.