Definition of Done (software) checklist template
For delivery teams closing a story, task, bug or sub-task. Required items cover merge to the main branch, review by another developer, updated tests passing in CI and acceptance criteria demonstrated, with docs, release notes and monitoring as optional checks.
- App: Checklist Flow for Jira
- Category: Software delivery
- Edition: Installs with or without a paid licence
- Items: 11 items, 5 required
- Suggested for: Story, Task, Bug, Sub-task
Items
#Build
| Item | Required |
|---|---|
| Code merged to the main branch | Required |
| Code reviewed and approved by at least one other developer | Required |
| Automated tests added or updated for the change | Required |
| All automated tests pass in CI | Required |
| No new linter or static analysis warnings | Optional |
Product
| Item | Required |
|---|---|
| Acceptance criteria met and demonstrated | Required |
| Product owner has seen the change | Optional |
| Feature flag state agreed (on, off or staged) | Optional |
Ship
| Item | Required |
|---|---|
| Documentation or help text updated | Optional |
| Release notes entry written | Optional |
| Monitoring and alerts cover the new behaviour | Optional |
Use it
#In a Jira work item, open the Checklist Flow panel, then Template library in the Templates section. Find the template under its category, use Preview to see the items and Install to add it to your site's templates. From then on you can apply it to any work item, or, with a paid licence, have it added automatically by issue type.
Related
#- Checklist Flow for Jira documentation
- Jira checklist templates: all 49 templates