Cycles
Team-scoped planning windows. Issues bind to at most one cycle.
8 operations
- GET
/api/cycles/{cycle_id}Get a cycle by id - PATCH
/api/cycles/{cycle_id}Update a cycle - GET
/api/cycles/{cycle_id}/carryoverWhat completing this cycle would do with the work still open in it - POST
/api/cycles/{cycle_id}/completeEnd a cycle and carry its unfinished work forward (idempotent) - GET
/api/cycles/{cycle_id}/issuesList issues in a cycle - PUT
/api/issues/{issue_id}/cycleBind an issue to a cycle, or unbind by passing cycle_id = null - GET
/api/teams/{team_id}/cyclesList cycles for a team (most recent first) - POST
/api/teams/{team_id}/cyclesCreate a cycle on a team