Stories
How each tracker story moved through review, and where it waited.
Stories, the third tab of Reports, looks at your work ticket by ticket instead of pull request by pull request. It lists every ticket with at least one pull request merged in the reporting window, how long the work took, how big it was, and whether its latest ticket review found the acceptance criteria met.
#What you need
An issue tracker connected to the workspace: Jira, GitHub Issues, Linear or Notion. The tracker links a ticket to its pull requests. Without one, the tab says Stories needs an issue tracker. Set it up in Settings → Integrations. The “met” verdicts come from ticket reviews; see Story checks.
#What you see
| Ticket | Working time | Pull requests |
|---|---|---|
| PAY-142 Partial refunds | 4.5 days | 3 |
| PAY-146 Rename ledger tables | 2 days | 2 |
| PAY-139 Refund reasons in the export | 0.5 days | 1 |
- Time and pull requests: for each ticket, the working time from its first pull request opened to its last one merged (in the workspace’s working hours), and how many pull requests it has, open, merged or closed. Each column has its own scale.
- Size and criteria: one mark per ticket, lines changed across its merged pull requests against how many acceptance criteria it has. Tickets that fell short are drawn hollow. A ticket with a pull request of unknown size is listed under the chart (Size unknown), not drawn; a ticket with no criteria is listed under No criteria found.
- The lists: Fell short (the latest ticket review found criteria not met, partly met or missing), Not reviewed (no ticket review yet) and Reviewed, no gaps. Open All n stories to see them; the split is shown before you open it.
The criteria count comes from the latest ticket review if there is one, else from the ticket’s criteria field, else from bullets under an “Acceptance criteria” heading in the ticket’s description.
#What you can do
- Open Reports and choose Stories.
- Select a ticket’s name to open it, with its pull requests, in a tab.
- Use the link beside a ticket to open it in your tracker.
- For a ticket under Not reviewed, open it and run a ticket review from the story view.
#Why it helps
Merged pull requests tell you code landed. Stories tells you whether the thing the ticket asked for was delivered, and it marks the tickets nobody checked, so a “done” column is not taken on trust.