Linear List Linear Issues

Lists non-archived Linear issues; if project_id is not specified, issues from all accessible projects are returned. Can filter by assignee_id. Only project_id and assignee_id server-side filters are supported; label, state, team, cycle, or date filters must be done client-side o…

料金

無料 Action

統合支払い

現在未対応

• afterstring
  Cursor for pagination (opaque string). Use the exact `endCursor` value from the previous response's `page_info` to fetch the next set of issues. Do not modify, prefix, or transform the cursor value in any way.
• firstinteger
  Number of issues to return. Maximum 250 per page. To retrieve all issues, loop using page_info.hasNextPage and pass page_info.endCursor as after until hasNextPage is false.
• project_idstring
  ID of the project to filter issues by. If provided, only issues belonging to this project will be returned. Must be a valid project ID that exists and is accessible to the authenticated user.
• assignee_idstring
  UUID of the user to filter issues by assignee. Use 'me' to filter by the current authenticated user, or provide a valid Linear user UUID (format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). Use LINEAR_GET_CURRENT_USER to get your own ID, or LINEAR_LIST_LINEAR_USERS to retrieve other…
• original_cursorstring
  The original cursor value before it was reset.
• include_transitionsboolean
  When true, includes the full status transition history for each issue, along with timestamps and computed time-in-state durations. When false (default), the tool returns the standard limited issue object with no transition data. Enabling this increases response size and GraphQL…
• cursor_was_corruptedboolean
  Indicates whether the pagination cursor was corrupted and reset.

• data

  必須
  Data from the action execution
• errorstring
  Error if any occurred during the execution of the action
• successfulboolean

  必須
  Whether or not the action execution was successful or not

検証済みの関連ユースケースはまだリンクされていません。