Cycles
Cycles group a team’s issues between a start and end date. Kuayle calculates progress, burndown and historical velocity from issue status data.
Cycle planning
Create a cycle with start and end dates, goals and an optional description. Add issues from the team backlog and review the issue list from the cycle page.
- Explicit start and end dates
- Goals and retrospective fields
- Issue assignment to active or upcoming cycles
Burndown and velocity charts
The cycle page plots completed and remaining issues across the cycle date range. Velocity history compares completed work across recent cycles.
- Burndown based on issue completion history
- Velocity history for up to 20 cycles
- Cycle totals for completed and cancelled issues
Carry over unfinished work
When completing a cycle, choose whether incomplete issues should move to the next upcoming cycle. If no upcoming cycle exists, the issues remain in the completed cycle.
- Carry-over is selected when the cycle is completed
- Requires an upcoming cycle for the same team
- Optional retrospective recorded on completion
Review Kuayle before you deploy it
Inspect the Apache 2.0 source, then follow the Docker Compose guide to run an instance on your infrastructure.