Definition of Ready Template for Jira [2026 Guide]
A practical DoR template with 9 criteria you can use in Jira today. Copy-paste ready, with examples for different team sizes.
A Definition of Ready (DoR)is a checklist of conditions that a user story or issue must meet before a Scrum team pulls it into a sprint. Think of it as a quality gate for incoming work: if the issue doesn't pass, it stays in the backlog until it does.
Without a DoR, teams regularly pull half-baked stories into sprints, leading to mid-sprint clarification meetings, scope changes, and preventable rework. Studies suggest that up to 30% of sprint capacity is wasted this way. If you want a quick way to spot an unready backlog before planning, see our companion piece 5 signs your backlog isn't ready for planning.
The 9-criteria DoR template
This template covers the most common readiness checks. Every criterion maps directly to a Jira field, making it easy to verify — manually or with automation.
| # | Criterion | Jira field | Why it matters |
|---|---|---|---|
| 1 | Has description (min 50 chars) | Description | Forces the author to articulate the problem or requirement |
| 2 | Has acceptance criteria | Description (section) or custom field | Defines "done" before work begins — prevents scope creep |
| 3 | Has estimate | Story Points or Time Estimate | Team has discussed complexity and committed to a size |
| 4 | Has assignee | Assignee | Someone is accountable for delivery |
| 5 | Has priority | Priority | Explicitly set (not "Medium" by default) — forces triage |
| 6 | Has labels | Labels | Enables filtering, reporting, and cross-team visibility |
| 7 | Has component | Component | Routes work to the right sub-team or domain |
| 8 | Has fix version | Fix Version | Ties work to a release — critical for release planning |
| 9 | Has linked issues | Issue Links | Dependencies are visible before work starts, not discovered mid-sprint |
Adapting the template for your team
Not every team needs all 9 criteria. Here's a quick guide by team maturity:
Starter (new to Scrum)
Start with just 3 criteria: description, acceptance criteria, and estimate. These deliver the most value with the least friction. Add more criteria once these three become second nature.
Growing (established Scrum practice)
Add assignee, priority, and component. This forces explicit triage and routing decisions during backlog refinement.
Mature (scaling across teams)
Use all 9 criteria plus custom ones specific to your domain. For example: "security review label applied", "API contract documented", or "UX mockup attached".
How to implement this in Jira
There are three approaches, from manual to fully automated:
Option 1: Manual checklist in description
Add a DoR checklist template to your issue description. Simple, but relies on discipline — teams inevitably stop using it after a few sprints.
Option 2: Jira Automation rules
Create automation rules that check field conditions and transition issues. Works for simple checks, but complex multi-condition rules become hard to maintain.
Option 3: Dedicated DoR app (recommended)
Tools like ReDo evaluate all criteria automatically and show a real-time 0–100% readiness score directly on the issue. The score updates on every field change — no manual checking needed. Custom formula-based criteria let you extend the template with any Jira field condition.
Common mistakes to avoid
- Too many criteria too soon. Start with 3–5 and add more as the team matures. A 20-item checklist will be ignored.
- Making DoR a gate for the PO alone. The whole team should agree on readiness during refinement.
- Not enforcing it.A DoR that exists in a wiki page but isn't checked before sprint planning is useless.
- Treating DoR as static. Review and adjust your criteria every quarter based on what causes the most rework.
Key takeaway
A Definition of Ready template is only as good as its enforcement. The best approach is to embed it directly into your Jira workflow so readiness is checked automatically, not manually. Start simple, iterate, and let the data show you where to add more criteria. For the companion checklist on the output side of work, see our Definition of Done template for Jira.