Summary
The issue search command does full-text search but does not support scoping results to a specific team. The underlying SearchIssues GraphQL API already accepts an IssueFilter (which includes team filtering), but the CLI does not expose it.
Motivation
Users want to search within a team context -- e.g. find issues matching a query but only within their team issues. issue list --team=X supports team filtering but not full-text search. Adding --team to issue search would bridge this gap.
Proposed change
Add --team flag to issue search (and potentially other filters like --assignee, --state, --priority) that constructs an IssueFilter and passes it to SearchIssues instead of nil.
The plumbing already exists -- SearchIssues in pkg/linear/client_issues.go accepts *IssueFilter, and issue list already has resolver logic for team names/keys.
Summary
The issue search command does full-text search but does not support scoping results to a specific team. The underlying SearchIssues GraphQL API already accepts an IssueFilter (which includes team filtering), but the CLI does not expose it.
Motivation
Users want to search within a team context -- e.g. find issues matching a query but only within their team issues. issue list --team=X supports team filtering but not full-text search. Adding --team to issue search would bridge this gap.
Proposed change
Add --team flag to issue search (and potentially other filters like --assignee, --state, --priority) that constructs an IssueFilter and passes it to SearchIssues instead of nil.
The plumbing already exists -- SearchIssues in pkg/linear/client_issues.go accepts *IssueFilter, and issue list already has resolver logic for team names/keys.