Definition of done
The checklist every item must meet before moving to Done, how to check it on the item's page and who configures it.
On this page
The definition of done (DoD) is the team's agreement on what "finished" means: for example, that the code has been reviewed by another person or that the documentation is up to date. It is the same for all items of a type, unlike Acceptance criteria and QA, which belong to each item.
Agile boards start with this definition of done, which the lead can change:
Acceptance criteria met (stories, tasks and bugs).
Reviewed by another person on the team (stories, tasks and bugs).
Documentation or release notes up to date (stories only).
Before you start
To check the list you must be a Lead, Member or QA of the desk.
Check an item's definition of done
Open the item's page.
Scroll down to Definition of done. Next to the title you see how many points you have checked out of the total, for example 1/3.
Check each point as it is met. Each check is saved by itself.
The list only shows the points that apply to the item's type. If no point applies, the section doesn't appear.
When moving to Done
When you take the item to Done, the platform checks that all its points are checked. If any is missing, the item doesn't move and you see the notice The definition of done isn't complete. On the board, the card goes back to its column.
The requirement is set by the target status. In the built-in configuration only Done has it, but the lead can turn it on in other statuses with the Requires DoD checkbox. See Board statuses and columns.
How the lead configures it
The desk's lead defines the list's points and which item types each one applies to, in Settings → Definition of done. See Definition of done and release to production.