Skip to content

jira cache boards

  • Usage: jira cache boards [flags]

Prime the per-profile boards cache and print its status. Use it before board-name completion, board-scoped issue listing, or any workflow that needs board IDs without repeated agile API calls.

The command serves a fresh cache entry unless --refresh is set. Large sites are capped by default; use --unbounded when you need every board and are prepared for a longer live read.

Pagination

--unbounded

Walk every page (disables the default 100-page / 10 000-board cap)

Cache

--refresh

Force a fetch even when the cache is fresh

--ttl-minutes <N>

Freshness window before automatic refresh

Default: 40320

Output fields

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

Field Type Description
boards_count integer
cache_empty boolean
cache_source_state string Disposition observed before any fetch (never the derived empty state).
cache_state string Effective disposition after the read: fresh, stale, missing, malformed, refresh, or empty.
fetched_at string (date-time)
from_cache boolean
primed boolean true when this invocation fetched from Jira and wrote the cache file.
profile string
truncated boolean
truncated_reason string
ttl_seconds integer

Examples

jira cache boards # (1)!
jira cache boards --refresh # (2)!
jira cache boards --unbounded # (3)!
  1. Use the boards cache if fresh, otherwise fetch from Jira
  2. Force a re-fetch even when the cache is still fresh
  3. Walk every page, ignoring the default 100-page cap