The Theme view
Tickets grouped by what they are about, so you can see where the sprint's effort goes.
The Theme view is the page This Sprint opens on. It puts the sprint’s tickets in rows by area of work, such as “Refunds” or “Ledger”, rather than by epic. Each row tells you in a sentence what that work involves, and its status columns show how far it has got.
#What you see
Partial refunds and the customer emails and exports around them. Development work.
Moving the daily ledger to new tables and retiring the old nightly job. Development work.
- One row per theme. AI names between three and eight themes for the sprint and puts every ticket in exactly one. Tickets that fit no theme go in a last row, No theme.
- The theme’s summary. One or two sentences on what the work involves and whether it is development work or other work, such as design, content or testing. The summary has no numbers.
- A colour bar. The row’s tickets by column. Hover over it, or move to it with the keyboard, to read the counts, for example “2 In progress, 3 Product review, 8 Complete” and “4 with a pull request, 9 without”. Limn counts these, not AI.
- Row order. Rows with the most pull requests come first. Each row header says its count, so you can check the order.
An arrow between two tickets is drawn as critical when the two sit next to each other on a critical path.
#What you can do
- Select a card to read its story in the panel on the right.
- Use the Has PRs and Needs code chips to hide tickets that will not reach the code, such as design or content tickets.
- Open a row’s Complete cell to see what that theme has finished.
#Before themes appear
Themes are written after AI reads the sprint, and a sprint needs at least six tickets. Until then, the view shows one row, All tickets, and a line that says why: “Themes appear after Claude reads the sprint.”, or that AI is off. Themes are written again only when the sprint’s tickets or their summaries change, so a status change costs nothing.
#Why it helps
Epics are often too big or too old to say what a sprint is doing. Themes are made fresh for each sprint from the tickets in it, so a manager can say “most of this sprint is refunds, and the ledger work has not started” with the counts to back it.