Open a ticket's story

The story view is Limn’s page for one ticket. It brings together what the tracker says, what the team said in the comments, what the pull requests deliver, and what is still missing. It works for any ticket on the workspace’s tracker, including a ticket with no pull request yet.

#Open it

The same story view opens in two places:

• In a panel on This Sprint. Select a card, a ticket key in a call-out, or a key in an answer. The panel opens on the right, over the board, so no card moves. Use the arrows in its header, or j and k, for the next and previous ticket, and Esc to close it. Drag its edge to make it wider.
• In its own tab, named “PAY-142 · Ticket”. Use the arrow in a card’s corner, Open ticket tab in the panel, a ticket chip on a pull request, the pull request’s Open story menu item, the Stories results of a search, or ⌘ K.

A pull request’s own Ticket tab shows the same content for each ticket the pull request names. See The pull request’s Ticket tab.

#What you see

The header

• The key, a link Open in Jira (or the name of your tracker), and the title.
• The status, the issue type and the assignee. On Jira the status is a menu, and on Jira, GitHub Issues and Linear the assignee is a menu (see below).
• Facts as chips: how many criteria are met (“3 of 4 met”), failing CI across the pull requests, and the number of pull requests.
• One line on how current the story check is (“1 PR changed since · checked 1 hour ago”) and, when one is due, when the next automatic check starts. Re-check runs one now.

On a wide screen these facts sit in a column on the right, with “On this page” links under them.

The Ticket section

Always open, in this order:

1. The summary and the criteria. After a story check: two or three sentences on how far the pull requests deliver the ticket, then each criterion with its status and the pull request that does it. Before any check: the criteria from the ticket, numbered, or “Worked out from the description” when the ticket has none written. See Acceptance criteria.
2. The design, when the ticket has two or more pull requests: a drawing of how the pieces fit. Draw design or Redraw design is in the section heading.
3. Asked for outside the criteria: what the ticket’s title or description asks for that no criterion covers and no pull request does.
4. Docs check, after you press Check against docs. See Check against docs.
5. As written in Jira (or your tracker): the ticket’s own text, closed until you open it.
6. Comments, open: the newest three, then Show all. See Ticket comments.

The pull requests

Under the Ticket section: every open pull request on the ticket as a card, as on Open pull requests, then Merged and, closed, Closed without merging. A ticket with none says “No pull requests for this ticket yet.” Pull requests in other workspaces are counted, not listed.

#What you can do

1. Press Re-check to run the story check again now.
2. Press Check against docs to compare the story with your docs library.
3. On This Sprint, press Implement on a not-started or in-progress ticket with no pull request to have AI plan and build it, or Fill gaps on a started ticket to build only the criteria the check found not met. Nothing is pushed until you press Push, unless you tick After the build: review and fix, then open the pull request. See Implement story.
4. On Jira, change the ticket’s status from the status menu.
5. On Jira, GitHub Issues and Linear, assign the ticket from the assignee menu.

#Change the status in Jira

On a Jira ticket the status chip is a menu. Opening it asks Jira which statuses the ticket can move to from here. Pick one and Jira changes the ticket at once; Limn then reads the status back and shows it everywhere.

#Assign the ticket

On Jira, GitHub Issues and Linear the assignee is a menu. Opening it asks your tracker who can be assigned this ticket: on Jira the people assignable in the ticket’s project, on GitHub the people assignable in the issue’s repository, on Linear the active members of the ticket’s team. Type to find a person, or pick Unassigned. The ticket changes at once; Limn then reads the assignee back and shows it everywhere, including the People board. If the tracker refuses, the menu shows the person you had before and says why in one line.

#Ask about this story

At the bottom of the story view, ask for advice about the ticket and its pull requests. Pick a ready-made question or type your own, then press Ask:

• How to test: what to do, step by step, to prove the ticket is done once its pull requests are merged, and what still needs doing.
• Integration: how the change fits with the other services, repositories, configuration and data.
• Risks and Criteria check.

The agent reads the ticket, each pull request’s changes and code, every repository in the workspace, the workspace’s reference documents and the sprint’s other stories. It also gets your Claude memory, CLAUDE.md and skills for these projects, the same ones Implement story uses (Settings → Sandbox). It only reads: it runs nothing and changes nothing. It gets ready when you open the story, so the first answer starts quickly, and closes after 10 minutes without use. Chats are saved with the story: pick an earlier one in the menu to read it or ask a follow-up.

#Why it helps

A ticket is often delivered by several pull requests in several repositories, and its real scope lives partly in the comments. The story view is the one place that holds all of it, so “is PAY-142 done?” has an answer you can check line by line.