Tasks

Test a task and report bugs

Q: When does a task count as passed?

When every tester chose Works and no bug is Open or waiting for Verify after Mark fixed.

Q: Why is the task failed even though I said it works?

Another tester chose Has bugs, or at least one bug is still Open.

I want to …

… have one or more people test a finished task, collect their verdicts, and track bugs until they are fixed.

Before you start

Testing belongs to Pro and Ultra. On Free the Testing chip shows a lock and opens the plans (Upgrade to enable Testing).
Any workspace member can be a tester, not just the people assigned to the task.
Only the tester themselves can set their verdict.
Anyone in the workspace can report a bug and mark it Mark fixed. Only the person who reported it, an Owner, or an Admin can confirm the fix with Verify or delete the bug.

Here's how

Open the task. The Testing card sits below the modules. If it is missing, tap the Testing chip with a plus icon below the description (Enable Testing).
Tap the avatar circle in the Testing header. A list of all workspace members opens. Tap a name to add or remove them as a tester. Removing a tester also drops their verdict. As Owner or Admin with a free seat, the list ends with Invite member.
Each tester is listed with their verdict: Not tested, Works, Has bugs, or Blocked.
If you are a tester, you see Your verdict. Tap Works when you found no problems. Tap Has bugs or Blocked if something is wrong or you cannot test at all. Tap the selected chip again to go back to Not tested.
To report a problem, tap Report bug under Bugs. Fill in Title and, if helpful, Steps to reproduce, Expected, Actual, and Environment (device, OS, browser, version). Pick a Severity: Minor, Major, or Critical. Tap Save. If you are a tester, your verdict switches to Has bugs.
After saving, the dialog stays open and Attachments accepts screenshots, videos, or files. In the browser you can also drag them straight onto the plus tile. The same file limits apply as for task attachments.
The list shows the newest bugs. Load more brings in older ones. Tap a bug in the list to edit it. Whoever fixed it taps Mark fixed or Won't fix. The reporter then checks it again and taps Verify, or Reopen if it still fails.
The header chip shows the overall state: In testing, Passed, Failed, or Blocked.
Once testers are chosen, the board card shows a testing symbol and how many testers have set any verdict, for example 1/2. The symbol is an hourglass while nobody has tested, a check mark for Works, a bug for Has bugs, and a block sign for Blocked. With several testers, Blocked wins over Has bugs, and Has bugs wins over Works. Hover over or long-press the symbol to see the state and the number of open bugs.
Tap the cross (✕) in the Testing header (Delete) and confirm to turn the module off. Testers and verdicts are cleared. Bugs are kept and come back when you enable Testing again.

The result

Everyone sees at a glance who has tested the task, what is still broken, and when all testers agree that it works.

Common questions

When does a task count as passed?

When every tester chose Works and no bug is Open or waiting for Verify after Mark fixed.

Why is the task failed even though I said it works?

Another tester chose Has bugs, or at least one bug is still Open.

Does duplicating a task copy the testing state?

No. The copy starts untested and without bugs.

Do older app versions break testing?

No. Older versions do not show the module, but they leave testers, verdicts, and bugs untouched.