Module issues 

Issue CRUD, list/search, batch create, and label convenience operations — IssuesService, obtained via LinearClient::issues.

Structs

IncomingRelation

An incoming issue relation: the owning issue is the target (e.g. it is blocked by issue).

Issue

A Linear issue with its commonly needed references embedded (state, team, people, labels, project placement, parent, and relation summaries).

IssueCreateInput

Input for IssuesService::create and IssuesService::batch_create. team_id and title are required; unset optional fields are omitted from the request.

IssueCreateInputBuilder

Use builder syntax to set the inputs and finish with build().

IssueSearchResult

One hit from IssuesService::search. This is Linear’s own IssueSearchResult GraphQL type (not Issue), so it carries a smaller field set plus search metadata.

IssueUpdateInput

Input for IssuesService::update. Every field is optional.

IssueUpdateInputBuilder

Use builder syntax to set the inputs and finish with build().

IssuesService

Issue operations. Obtained via LinearClient::issues; Copy, so it can be freely captured by pagination closures.

ListIssuesRequest

Request for IssuesService::list. All fields are optional; the server page size defaults to 50.

ListIssuesRequestBuilder

Use builder syntax to set the inputs and finish with build().

OutgoingRelation

An outgoing issue relation: the owning issue is the source (e.g. it blocks related_issue).

SearchIssuesRequest

Request for IssuesService::search. Only term is required.

SearchIssuesRequestBuilder

Use builder syntax to set the inputs and finish with build().