Problem
The bd linear integration only supports a single linear.team_id config value. Users who contribute across multiple Linear teams — particularly when a parent/org team and a child/domain team are both active — have no way to sync from both in a single workflow.
Use Case
A common setup:
- Parent team: org-level tickets — dev-prod, shared platform, cross-cutting concerns
- Child team: domain-specific work
A contributor participates in both teams. Today they must either pick one team to sync or manually swap linear.team_id and run bd linear sync twice, which is error-prone and cumbersome.
Proposed Solution
Support multiple teams via one of:
- Array config:
bd config set linear.team_ids "uuid1,uuid2" (comma-separated or repeatable)
- CLI flag override:
bd linear sync --team uuid1 --team uuid2
- Both: array config as default, flag for ad-hoc overrides
Issues pulled from multiple teams should be merged into the local beads database normally, with external_ref tracking which Linear team each issue belongs to.
Workaround Today
None clean. Single linear.team_id only.
Problem
The
bd linearintegration only supports a singlelinear.team_idconfig value. Users who contribute across multiple Linear teams — particularly when a parent/org team and a child/domain team are both active — have no way to sync from both in a single workflow.Use Case
A common setup:
A contributor participates in both teams. Today they must either pick one team to sync or manually swap
linear.team_idand runbd linear synctwice, which is error-prone and cumbersome.Proposed Solution
Support multiple teams via one of:
bd config set linear.team_ids "uuid1,uuid2"(comma-separated or repeatable)bd linear sync --team uuid1 --team uuid2Issues pulled from multiple teams should be merged into the local beads database normally, with
external_reftracking which Linear team each issue belongs to.Workaround Today
None clean. Single
linear.team_idonly.