Cycles and sprints
Cycles and sprints, planned for RyTask — time-boxed batches of work with start and end dates and automatic rollover of unfinished items into the next cycle.
RyTask plans cycles — time-boxed batches of work (call them sprints or iterations if you prefer). The detail that matters most is auto-rollover: when a cycle ends, unfinished items carry forward to the next one automatically, instead of demanding a manual grooming session. Teams that use Linear consistently name this as the feature they love; almost everywhere else it is busywork.
What's planned:
- Time-boxed cycles — recurring work batches with start and end dates (MVP scope).
- Auto-rollover of unfinished work — incomplete items move forward on their own (MVP scope).
Custom fields
Custom fields, planned for RyTask — text, number, select, date, and user fields on work items first, with validation and computed fields later. No usage caps.
Milestones and roadmap
Milestones, planned for RyTask — named delivery targets with fixed dates per project, plus a quarter-level roadmap view and OKR-style goals in a later wave.