Definition of done and release to production
Configure the definition of done checklist and decide whether releasing a version requires an approved change in a service desk.
On this page
Two settings protect the quality of what the team delivers: the definition of done, which is required of each item before moving to Done, and the release to production, which can require an approved change before releasing a version.
Before you start
You must be the desk's Lead or manage the company's desks.
To require a change, the company must have a service desk where changes are managed (an IT help desk, MDA).
Configure the definition of done
Go to Settings → Definition of done.
To add a point, press Add item and enter the text, for example Automated tests up to date.
Below each point, check the types it applies to: Story, Task, Bug, Epic and Subtask. A new point comes checked for stories, tasks and bugs.
Order the points with ↑ and ↓, and delete the ones you don't need with Remove.
Press Save definition of done.
You see the notice Definition of done saved.
Rules
Up to 30 points, of up to 300 characters each.
Each point needs text and at least one item type.
If the list is left empty, you see No definition of done: entering Done requires nothing else.
The list is required when entering the statuses that have the Requires DoD checkbox checked (by default, Done). See Board statuses and columns.
Configure the release to production
Go to Settings → Board and scroll down to Going to production.
In Releasing a version requires an approved change in, choose the service desk where changes are managed. To not require it, choose No change required.
If you chose a desk, in Change type choose:
Standard (pre-approved): for routine deliveries that already have prior approval.
Normal (goes through the CAB): the change advisory board reviews each delivery.
Press Save.
What happens next
With a required change, pressing Release on a version creates a change in that desk, with the chosen type and the list of items, and the release stays Waiting for the change until it is approved. See Release a version.
Whoever releases needs access to the chosen service desk. If they don't have it, they see a notice saying so.
Without a required change, Release marks the version as Released right away.