Overview
Sprints lives at Dashboard → Sprints and is shared across your whole studio. Issues are typed (Story, Bug, Task, Spike…), assigned to studio members, estimated, and pulled into time-boxed sprints.
Studio tier
Backlog
The backlog (Sprints → Backlog) is the unsorted pool of every issue not in an active sprint. Use it to:
- Capture incoming work without committing to a sprint yet.
- Triage and re-estimate before planning.
- Bulk-move issues into the next sprint when you start planning.
Active sprint
The main Sprints view shows the currently active sprint as a kanban board with columns for To do, In progress, In review, and Done. Drag issues between columns to update status - every change is logged.
Create a new sprint with New sprint, set its date range, and pull issues from the backlog. Closing a sprint moves any unfinished issues back to the backlog (or forward to the next sprint, your choice).
Issues
Click any issue to open its detail dialog. Issues support:
- Type, priority, status, assignee, reporter.
- Estimate (story points or hours).
- Markdown description with screenshots and code blocks.
- Activity log + threaded comments.
- Linked issues (blocks / blocked-by / duplicates).
Timesheet
Sprints → Timesheet lets each member log time against issues they're working on. Logged time rolls up to the issue, the sprint, and the per-member report. Useful for invoicing contractors or just tracking where the studio's time goes.
Reports
Sprints → Reports shows per-sprint:
- Burndown - remaining estimate vs ideal line.
- Velocity - completed points across recent sprints.
- Throughput - issues closed per day.
- Time logged - hours per member, per type.
Use the velocity chart to right-size your next sprint commitment.