See the current sprint

This Sprint is one board for the sprint your team is working in now. Limn reads the sprint’s tickets from your issue tracker, joins each ticket to the pull requests that name it, and lays the tickets out by status. You see in one place what is not started, what is in review, what waits on another ticket and what is done.

#What you need

This Sprint needs an issue tracker for the workspace. Set one up in Settings → Integrations → Issue tracker. Without one, the page shows one line, “Connect Jira, Linear or GitHub Issues to see this sprint.”, and a Set up in Settings button.

Each tracker gives the sprint in its own way:

• Jira: the open sprint of the projects the workspace reads. Set your Project keys so Limn knows which projects to ask about.
• Linear: each team’s active cycle.
• GitHub Issues: the current iteration of a GitHub Projects board, else the nearest open milestone that is due.
• Notion: the sprint property you map in Settings.

When the tracker has no sprint, or none is active, Limn shows the To do and In progress tickets edited in the workspace’s reporting window instead, and the title says so.

#What you see

The page has three views, Theme, Critical path and People. Each one is the same board with the tickets in different rows. Press 1, 2 or 3 to switch. The picture below is a working model of the board with made-up tickets: select a view to see the rows change.

The toolbar

• The sprint’s name and its dates, for example “14 Oct – 27 Oct · day 4 of 14”.
• The number of tickets in the sprint.
• Ask Claude (or Ask Codex, if Codex is your AI provider): ask a question about the sprint. See Ask about the sprint.
• Statuses (the gear): choose which tracker statuses go in which column. See Columns and statuses.
• Refresh: read the sprint from the tracker now.

#Columns and statuses

The columns are Not started, In progress, Code review, Product review and Complete. Limn puts each tracker status in a column by itself, using the status’s category in the tracker. If your board has its own stages, press Statuses to add, rename, reorder or remove columns, give each column a meaning, and drag each status into the column it belongs to. A switch in the same editor moves a ticket from Code review to Product review when all of its pull requests have merged. Reset to automatic goes back to Limn’s own columns. A status that is new on your board since you saved is marked “not placed yet”.

The Complete column is closed at first, to save room. Press Show to open it, or press a row’s ticket count to open that row only.

#Ticket cards

Every card has the same shape on every view:

• The ticket key and title.
• One line that says what the ticket delivers, written by AI from the ticket.
• The criteria line: “3 of 4 criteria met” from the latest story check, or “4 criteria” when no check has run yet. It is in italics when the check ran before the latest changes.
• The assignee (on the People view, the theme instead). “Unassigned” when nobody has it.
• Tags in words: CI failing, No PR, “2 PRs · 1 open”, No owner.

Small marks beside the key show the rest: a pull-request mark when the ticket has an open or merged pull request, a route mark when it is on a critical path, and an hourglass when it waits on another ticket that is not finished. A ticket from outside the sprint is drawn faint. Inside each cell, tickets with a pull request come first. The key under the board names every mark the board uses.

Arrows go from a ticket to the ticket that waits on it. They come from the tracker’s own “blocked by” links and from what the ticket text says. A number on an arrow points to the reason in the line under the board. Hover over an arrow or its number to read it.

#Filters

Two chips above the board narrow every view. Has PRs keeps tickets with at least one pull request. Needs code keeps tickets with a pull request and the not-started tickets that AI thinks will need code changes; a ticket not judged yet says “Not judged yet”. With both on, a ticket must pass both. The pace figures and the count table always count the whole sprint. Your choice is kept in this browser.

#What you can do

1. Select a card to read its story in the panel on the right. See Open a ticket’s story.
2. Select the arrow in a card’s corner to open the ticket in its own tab.
3. Press the hammer button on a not-started or in-progress ticket with no pull request (Implement), or Fill gaps on a started ticket whose check found criteria not met. See Implement story.
4. Press Refresh to read the sprint again. With AI on, Refresh also starts up to three story checks for tickets whose check is missing or out of date, and says how many it started. A ticket whose last check found every acceptance criterion met is skipped, unless the ticket text has changed since.
5. Press ⌘ K and type a ticket key to show that ticket’s story, or to run Refresh, Ask or Statuses.

#How it stays current

Limn reads the sprint in the background about every 20 minutes, but only for a workspace whose This Sprint page someone opened in the last 7 days. Opening the page does not call the tracker. While the page is open it checks once a minute whether anything changed and redraws only then, so the board does not jump while you read it.

#Why it helps

A tracker board says what people set the status to. This Sprint also says what the code says: which tickets have pull requests, which have failing CI, which criteria the code meets, and which tickets wait on others. That makes it a good page for a stand-up or a mid-sprint check, and it needs no extra data entry.

If you do not use sprints, hide the page in Settings → Features. Sprint length and the comparison window are in Settings → Reports and sprint.