Type / Priority
Feature / Medium-High
Summary
There is no "complete cycle" workflow, and no way to transfer unfinished work items to another cycle when a cycle ends.
Current state (evidence)
- Cycle status is purely date-derived (
service/cycle.go computeCycleStatus:15-38); there is no user "complete cycle" action, no transfer endpoint, and cycles.progress_snapshot (...up.sql:328) is never captured.
Proposed scope
Add .../cycles/:cycleId/transfer-issues/ to move incomplete (backlog/unstarted/started) issues to a chosen next cycle, persist progress_snapshot at completion, and add a "Complete cycle" UI action + transfer modal.
Type / Priority
Feature / Medium-High
Summary
There is no "complete cycle" workflow, and no way to transfer unfinished work items to another cycle when a cycle ends.
Current state (evidence)
service/cycle.gocomputeCycleStatus:15-38); there is no user "complete cycle" action, no transfer endpoint, andcycles.progress_snapshot(...up.sql:328) is never captured.Proposed scope
Add
.../cycles/:cycleId/transfer-issues/to move incomplete (backlog/unstarted/started) issues to a chosen next cycle, persistprogress_snapshotat completion, and add a "Complete cycle" UI action + transfer modal.