Skip to content

jira issue list

  • Usage: jira issue list [flags]

Build an issue-search JQL query from flags, profile defaults, board scope, and optional custom JQL, then list matching Jira issues. Use it for the main terminal issue triage workflow.

--as-jql is an offline preview that does not contact Jira or resolve credentials. --count calls Jira for an approximate match count without fetching issues. Issue-key ranges are expanded and chunked so large key lists return per-chunk errors without discarding successful chunks.

Filters

--assignee <USER>

Restrict by assignee; use me for the current user

Allowed values:

  • me — current user
  • none — unassigned

--board <NAME>

Restrict to issues whose project belongs to the named board (case-insensitive exact match against the cache)

--board-id <ID>

Restrict to issues whose project belongs to the board with this id

Default: 0

--created <DATE>

Filter by created date (same grammar as --updated)

--epic <KEY>…

Restrict to issues in epic keys

--jql <JQL>

Run a custom JQL query for the issue list [example: status = Done AND assignee = currentUser()]

--key <KEY>…

Restrict to issue key, comma list, or PROJ-1..PROJ-5 range

--label <NAME>…

Restrict by label

--priority <NAME>…

Restrict by priority

--project <KEY>…

Restrict to Jira project key

--reporter <USER>

Restrict by reporter; use me for the current user

Allowed values:

  • me — current user

--resolved <DATE>

Filter by resolved date (same grammar as --updated)

--status <NAME>…

Restrict by status: name, category comparator (<Done, >=In Progress), or negation (!Abandoned)

--type <NAME>…

Restrict by issue type

--updated <DATE>

Filter by updated date: -7d, 2026-01-01, >=2026-01-01, or A..B range

Sort

--desc

Sort descending

--order-by <FIELD>

Sort field

Allowed values:

  • updated — last-updated time (default)
  • created — creation time
  • priority — priority level
  • status — workflow status
  • key — issue key
  • summary — title text

Pagination

--all

Walk every page until isLast (bounded; use --unbounded to lift the caps)

--cursor <TOKEN>

Resume from a nextCursor returned by a previous page

--limit <N>

Page size requested from Jira

Default: 50

--unbounded

With --all, lift the default 100-page / 10 000-issue caps

Output

--as-jql

Print the built JQL query without calling Jira

--columns <COLS>…

Select and order columns for human/TSV output

Allowed values:

  • key — issue key
  • summary — title text
  • status — workflow status
  • assignee — assigned user
  • priority — priority level
  • updated — last-updated time

--count

Return only the approximate match count, without fetching issues

--detail

Fetch full issue records

--tsv

Render as tab-separated values for scripts (off a TTY this implies --output=human)

Execution

-p --parallelism <N>

Maximum concurrent requests (1-16)

Default: 1

Output fields

With --output json, the response envelope's data object carries these fields. Run jira schema for the full machine-readable schema.

Field Type Description
board_scope.applied boolean
board_scope.id integer
board_scope.name string
board_scope.project_keys array
board_scope.type string
detail boolean
failed_key_chunks[].error object Fields: code, field, flag, hint, http_status, message, …
failed_key_chunks[].key_expr string
issues[].assignee object | null Fields: account_id, display_name
issues[].key string
issues[].priority string | null
issues[].status string
issues[].status_category string Workflow category key (new, indeterminate, done); empty when the status carries none.
issues[].status_color string Status category color name; empty when the status carries none.
issues[].summary string
issues[].updated string (date-time)
jql string Present for board-scoped lists; the JQL the query resolved to.
precedence string Present for board-scoped lists; which scope source won when several were set.
succeeded_key_chunks integer Present when chunked --key reads partially fail.

Examples

jira issue list --project PROJ --status '!Done'
jira issue list --assignee me --type Bug --status "In Progress" --updated -7d # (1)!
jira issue list --jql "status = Done AND assignee = currentUser()" --count # (2)!
jira issue list --project PROJ --status Done --as-jql --output=json # (3)!
  1. List your in-progress bugs updated in the last week
  2. Ask Jira for an approximate count without fetching issues
  3. Preview the generated JQL without contacting Jira