Acceptance criteria and QA
Define an item's acceptance criteria and review it in QA criterion by criterion to approve it or reject it with a reason.
On this page
Acceptance criteria say what an item must meet to be accepted. In QA, a person with the QA or Lead role reviews the item against those criteria and decides: they approve it so it can move to Done, or reject it and it goes back to In progress. No item reaches Done without going through this step.
Define the criteria
Before you start
You must be a Lead, Member or QA of the desk.
The item must not be in QA: while it is under review, the criteria can't be edited.
Steps
Open the item's page.
In Acceptance criteria, press Edit.
Write the first criterion. To add another, press Add criterion. To delete one, press Remove next to it.
Press Save criteria, or Cancel to discard the changes.
Write criteria that can be checked with a yes or a no, for example The customer receives a confirmation email when paying. An item allows up to 50 criteria.
Each saved criterion shows its last QA result on its left: ✓ if met, ✗ if not met and · if not reviewed yet.
Review an item in QA
Before you start
You must have the QA or Lead role in the desk. Only those people see the review panel.
The item must be in a QA status (for example, the board's QA column).
Approve
Open the item's page. You see the QA · cycle panel with the review cycle number.
For each criterion, choose Met or Not met. If you want, write a Note (optional).
When all criteria are Met, press Approve.
You see the notice Approved in QA. The item stays in QA, ready for you to move it to Done from the board or from its Status.
If the item has no criteria, the panel says so and you can approve or reject it anyway (a rejection always has a reason).
Reject
In the QA · cycle panel, mark each criterion as Met or Not met. At least one must be Not met, unless you create a bug.
Press Reject….
Write the Reason for rejection.
If the problem is a separate defect, check Create a linked child bug (separate defect) and fill in Bug title, Severity and Bug description.
Press Reject and send back to In progress. If you change your mind before sending it, press Back.
Mark a result on all criteria before approving or rejecting. If any is missing, the review isn't saved.
What happens after a rejection
The item goes back to In progress and adds a bounce: its card shows ↺ with the number of rejections.
The item's assignee gets an internal note with the reason and the list of criteria that aren't met.
If you created a bug, it is linked to the item, in the same sprint and the same epic, and you see the notice Bug … was created with its number.
A new QA cycle starts: the next time the item reaches QA, it is reviewed again from scratch.
During the 24 hours after the rejection, the item counts as at risk.
QA history
On the page, QA history shows each review: the cycle, whether it was approved or rejected, who did it, when and the reason for rejection. Everyone who can open the item sees it, not just QA.
The QA bounces of a whole sprint are shown in the sprint's details. See Follow a sprint.
Related
Refine a story with Elion: so Elion proposes criteria
Board statuses and columns: which status requires QA