For business analysts

Write the story and its acceptance tests together

Capture what the client asked for, turn it into stories with acceptance criteria, and link the tests that prove each one, so nothing gets lost between analysis and QA.

Stories with acceptance criteria

Write stories in Markdown with templates for the formats you use, and link them to epics and releases.

A story with its description, tests and pull requests

Tests that prove each story

Link test cases to the story while you write it. QA sees exactly what has to be proven.

Traceability from stories to test cases and their latest results

Prioritise and estimate together

Order the backlog by dragging, and size stories with the team using planning poker.

The backlog in priority order

Questions

Can we keep specs and meeting notes here too?
Yes. Each project has docs with templates, reviews and links to the issues they describe.
Can clients raise requests directly?
Yes. Client users can raise issues through the portal, and they wait in triage until someone accepts them.
Is there a template for a user story?
Yes. Issue templates prefill the description, type, labels and sub-tasks, and doc templates cover specs and notes.

Try it with your own project

Free for up to 10 users. Team and Delivery start with 30 days free, no card needed.