Guide for business analysts

Shape the backlog

1. Create an Epic for each feature or client requirement. Press C, choose Epic as the type and give it a clear name such as UPI payments.
2. Under it, create Stories. In the New issue window, choose the epic in the Epic field. Write the story as the user would say it: As a customer I can pay a UPI ID so that…
3. Put the acceptance criteria in the description as a checklist. Markdown checklists work:

- [ ] A wrong UPI ID shows "This UPI ID doesn't exist"
- [ ] Payments over ₹1 lakh ask for the UPI PIN twice

4. Rank the backlog. In Backlog, drag rows so the most important work is on top. The team plans sprints from the top down.

The epic's page lists all its stories and how many are done. Epics also appear on Roadmaps and in Portfolio.

Keep requirements in docs

Each project has Docs for longer writing: requirement documents, PRDs, process notes and meeting decisions. Start from the PRD template, link the doc to its epic and stories, and ask a lead to review it before you publish. See Docs.

Make sure every story is tested

Open a story and look at Quality. It lists the test cases that cover the story and their last result. A story with no test cases says so. Work with QA so that each acceptance criterion has a case.

In Tests, the Covers column shows which stories each case tests.

Sort incoming requests

Client requests and incidents raised by others land in My work › Triage. Accept the ones the team will do, choosing the project and status they go to, or Decline the rest.

Prepare release notes

When a release is close, open it from Releases and choose Draft from done work to start the release notes from the issues that are done, then edit the wording for the client. See Releases and client reports.