Linear (API key)

Writes

• Create issue

  read back

  linear-key-create-issue

  Create one issue in a team, with a title and optionally a markdown description, priority, assignee, state, labels and due date. Returns its id, identifier and url.

• Update issue

  read back

  linear-key-update-issue

  Update one issue's title, description, priority or due date. Give at least one; the fields you leave out do not change.

• Assign issue

  read back

  linear-key-assign-issue

  Assign one issue to a user.

• Move issue

  read back

  linear-key-move-issue

  Move one issue to another workflow state of its team, such as In Progress or Done.

• Add issue label

  read back

  linear-key-add-issue-label

  Add one label to an issue, keeping its other labels.

• Remove issue label

  read back

  linear-key-remove-issue-label

  Remove one label from an issue, keeping its other labels.

• Add comment

  read back

  linear-key-add-comment

  Add one comment, in markdown, to an issue. Linear notifies the issue's subscribers and anyone mentioned. Returns the comment's id and url.

• Archive issue

  read back

  linear-key-archive-issue

  Archive one issue. It leaves the team's views and lists, and can be restored in Linear.

Reads

• List teams

  linear-key-list-teams

  List the teams whose issues the key's user can see. Returns 50 a page, each with id, key (the prefix of issue identifiers, such as ENG) and name. When pageInfo.hasNextPage is true, pass pageInfo.endCursor as after. A GraphQL query that changes nothing.

• List workflow states

  linear-key-list-workflow-states

  List one team's workflow states (its issue statuses), 50 a page. Each has id, name, type (triage, backlog, unstarted, started, completed, canceled or duplicate) and position. Use a state's id with move-issue or in a list-issues filter. A GraphQL query that changes nothing.

• List labels

  linear-key-list-labels

  List the issue labels the key's user can see, of the workspace and of every team, 50 a page. Each has id, name, whether it is a group, and its team (null for a workspace label). A team label can be added to issues of that team. A GraphQL query that changes nothing.

• List issues

  linear-key-list-issues

  List issues, 25 a page, ordered by creation time, or by last update when order_by is updatedAt. Filter by team, state (by id or type), assignee (by id, the key's own user, or unassigned), label, priority, title text and last update. Each issue has id, identifier, title, priority, url, due date, state, team, assignee and up to 10 labels; descriptions are left out, use get-issue. Archived issues are left out. When pageInfo.hasNextPage is true, pass pageInfo.endCursor as after. A GraphQL query that changes nothing.

• Search issues

  linear-key-search-issues

  Search issues by text in their title and description, and in their comments when include_comments is true. Returns 25 a page, ranked by relevance, with the same fields as list-issues and the same filter. team_id ranks one team's issues higher; it does not filter (use filter.team for that). Linear rate-limits this search more tightly than other queries (30 a minute by its schema). When pageInfo.hasNextPage is true, pass pageInfo.endCursor as after. A GraphQL query that changes nothing.

• Get issue

  linear-key-get-issue

  Get one issue by id or identifier (ENG-123): title, description (markdown), priority, url, due date, estimate, state, team, assignee, creator, project, parent, labels (up to 50) and when it was created, updated, completed or archived. A GraphQL query that changes nothing.

• List issue comments

  linear-key-list-issue-comments

  List the comments on one issue, 20 a page, in the order they were made. Each has id, body (markdown), author, when it was created and edited, and the comment it replies to. When pageInfo.hasNextPage is true, pass pageInfo.endCursor as after. A GraphQL query that changes nothing.