BriefFlow

Search documentation

Search BriefFlow's documentation by page title, section heading, or content.

What this does

Tasks that require QA (the default) can't reach Done without passing through a testing cycle. Every cycle — passed or not — stays on the task's permanent record.

Before you begin

Starting or completing a QA cycle requires the tasks.perform_qa permission (Testers by default). The task must be in Ready for QA to start a cycle.

Starting a QA cycle

Administrator permission required

Requires the tasks.perform_qa permission.
  1. Open a task that's Ready for QA.
  2. Select Start QA.
  3. Enter the environment you're testing in (e.g. Staging, Production).
  4. Select Start QA — the task moves to QA In Progress and a new cycle number begins.

Recording the result

  1. Work through the task's acceptance criteria.
  2. Open the task and select Complete QA.
  3. Choose Passed or Changes Required.
  4. Describe what you tested under Steps tested.
  5. If requesting changes, describe what needs to change — this field is required for a Changes Required result. Optionally add specific defects found.
  6. Submit.

What happens next

Passed moves the task toward Ready for Release. Changes Required returns the task to In Progress with your notes visible to the assignee, and this cycle's record stays on the task permanently — including its notes and any defects logged.

A full QA history — both the failed first cycle and the passing retest stay on the record.

Retesting

If changes are requested, fixing them and moving the task back to Ready for QA and starting a new QA cycle doesn't reopen or overwrite the previous one — it's a fresh cycle with its own number.

QA history is permanent

Every QA cycle — passed or not — stays visible on the task's record once it's completed. A task that needed three attempts before passing keeps all three cycles visible, not just the final Passed result. This is deliberate: it's an honest record of how much rework a task actually took, useful for spotting patterns in Reporting without erasing history.

Tip

Write "Steps tested" as if someone else needs to reproduce your test later — specific actions, not "tested the feature."

Common issues

I can't start QA on a task. It must be in Ready for QA status first — the developer needs to move it there.

Complete QA won't submit with Changes Required selected. The "what needs to change" field is required for that result — it's optional only when the result is Passed.

Related guides