The Tracker is now Build › Stories
The Tracker is now Build › Stories: every story and bug of the product in one list, whatever the old tracker setting was. Old Tracker links open it. See Build › Features and Build › Stories.
- The list: each story's "As a…" line, its feature, its type, status, acceptance checks, points, sprint, priority, its Jira issue, its owner and when it last changed. Views: Open, Ready, In build, Needs criteria, Bugs, Not in Jira (when Jira is connected), Done and All. Group by feature (the default), status, owner, team or area; filter by feature, status, type, owner, team, area, points, sprint or outcome. Search finds titles, keys and Jira keys.
- The kanban view is the board (List · Board): the same seven columns, Draft, Ready, In build, Ready for QA, In QA, Waiting for acceptance and Done. Without Linear or Jira, the board is your tracker: drag a card, or use its Move to.
- A story or bug opens in a drawer from its row, and has its own page: its description, acceptance checks, a bug's details (severity, steps to reproduce, environment, expected and actual, versions), its files, its Jira issue and the commits that named it.
Ready means ready. A story moves to Ready, or into In build, only with at least one acceptance check and an approved spec; one that moved on before checks existed says Needs criteria and keeps its status.
Creating stories. From a feature's Stories tab, or have Mind write them with the spec (see The spec interview).
With Linear or Jira. A product's stories follow one ticket system. A story sent to Linear follows its issue and doesn't drag (see Linear); a story in Jira moves both ways while Jira's Two-way sync is on (see Jira). The board's More menu has Sync with Linear now, Export CSV and Linear and Jira (Settings › Connections).
The product setting Stories and bugs in today's tracker (Settings › Product) no longer hides anything: Build › Stories shows them either way.