Skip to main content
ActiveMar 24Apr 4

Sprint 14

3 of 7 complete43%
In Progress2
PRJ-128Fix auth token refresh on expired sessions
PRJ-131Add rate limiting to public API endpoints
Review2
PRJ-125Migrate user preferences to Postgres JSONB
PRJ-134Update changelog for v2.4 release
Done3
PRJ-119Implement webhook retry with exponential backoff
PRJ-122Add org member count to billing dashboard
PRJ-116Fix SSO callback race condition
Sprints let you scope a fixed window of work within a project. Each sprint has a name, start date, end date, and a set of assigned tickets. A progress bar tracks how many tickets have reached a resolved column.

Creating a sprint

Open the Sprints dropdown from the project header (or press S) and click Create. Give the sprint a name and pick a start and end date. A sprint’s status badge updates automatically to Active, Completed, or Overdue based on the date range and whether unresolved tickets remain.

Managing tickets

Click Manage on the sprint bar or the edit icon in the dropdown to open the sprint detail panel. From there you can add tickets via the side panel, which lists every ticket in the project not already assigned to a sprint, grouped by status. Search by title or ticket ID to find specific tickets. Remove a ticket by hovering its row and clicking the remove button. When a sprint is selected and you click the + button in the project header, you get two options: Create ticket (opens the standard create modal) or Add to [Sprint] (opens the manage panel directly).

Viewing sprint tickets

Sprints integrate with both project views:
  • Kanban — Select a sprint from the dropdown to filter the board to only that sprint’s tickets. A bar below the header shows the sprint name, date range, and a Manage link. The board automatically includes resolved tickets regardless of age so you can see the full sprint scope.
  • List — Toggle one or more sprints from the dropdown. Sprint tickets appear in their own collapsible section above the regular status groups, sorted by status then priority. Drag and drop tickets between sprints and status groups.
Your sprint selection persists per project across sessions.

Using Janet to manage sprints

Ask the Janet Agent to handle sprint operations in natural language.

Create a sprint

“Create a sprint called ‘Sprint 8’ starting next Monday”

Add tickets

“Add SW-42 and SW-43 to Sprint 7”

View sprint tickets

“Show all tickets in the current sprint”

Create and assign

“Create 3 tickets for the auth feature and add to current sprint”