Repository navigation
Issue trackers: bind a project to more than one Linear team #38033
NeilMazumdar
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
What I want
Let a project read issues from more than one Linear team.
Why
Settings → Issue trackers binds a project to one Linear team.
issue_tracker_bindingshasproject_idas its primary key, andlistIssuesfilters onteam.key eq scope. One repository often holds work tracked across several teams. Today the issues panel andlist_issuesshow only the bound team, andcreate_issuecan file only there. An agent can still read and link an issue from another team by its key, but it cannot find that issue by listing or searching.What would cover it
Any of these would work for us, in order of preference:
teamargument increate_issue.Version
v0.1.11-nightly.20261117.4825, Linux x64.
Related
#30981 asks for a backlog board across trackers. #37967 covers Linear issue URLs. Neither covers binding more than one team.
All reactions