Skip to main content
Cycle (sprint, iteration, version, release) — a time-boxed grouping of items. Cycles attach to a board and accumulate items via cycleId on each item. Used for planning views, burn-down reports, and per-sprint filtering.

Sample JSON

Copy, edit, paste. Server-set fields (id, created, tenantId, …) are omitted from the example — they’re populated by the server on response.

What Ekso fills in

These fields are managed by the server. You don’t pass them on writes — they appear on the response.
  • items — Maintained automatically — each item carrying cycleId == <this cycle's id> shows up here.

Fields

Used by

Request body

  • POST /api/board/{boardId}/cycle
  • PUT /api/board/{boardId}/cycle/{cycleId}

Response body

  • GET /api/board/cycle
  • GET /api/board/{boardId}/cycle/{cycleId}
  • GET /api/board/{boardId}/cycle

CLI

ekso cycle — see the command branches page for available verbs. Body for create / update verbs typically passed via --data @file.json matching the sample JSON above.