Documentation

Everything you need to know about setting up and using ReDo — Definition of Ready & Done for Jira Cloud.

Overview

ReDo automatically evaluates every Jira issue against configurable quality criteria for Definition of Ready (DoR) and Definition of Done(DoD). It calculates a 0–100% readiness score and surfaces it directly in Jira — on issue panels, in custom fields, and on a sprint-level dashboard.

The app runs entirely on the Atlassian Forge platform. No data leaves Atlassian infrastructure. Configuration is stored per-project in Forge KVS, and scores update in real-time as issues change.

Installation & Setup

  1. 1
    Log into Jira as an admin— You need admin permissions to install apps. If you are not an admin, select "Try it Free" and then "Submit request" to request installation from your admin.
  2. 2
    Find the app — Select the Apps dropdown menu from the top navigation bar and choose Explore new apps. Search for "ReDo — Definition of Ready & Done for Jira".
  3. 3
    Install — Select the app tile, then click Try it Free to install. Once installed, you will see a success message.
  4. 4
    Open any issue— The ReDo panel appears automatically in the issue context. With default rules enabled, you'll immediately see a readiness checklist.
  5. 5
    Customize (optional)— Go to Project Settings → "Definition of Ready/Done Settings" to toggle built-in rules, add custom criteria, and choose your app mode (DoR only, DoD only, or both).

No external services or API keys required. The app works out of the box with sensible defaults.

Issue Panel

The issue panel is embedded in every Jira issue context. It displays:

  • A readiness score (0–100%) with color indicator: green (100%), orange (50–99%), red (<50%)
  • Auto-evaluated rules — built-in checks with pass/fail status and details
  • Custom criteria — manual checkboxes and formula-based checks

When running in "both" mode, the panel shows separate tabs for DoR and DoD. The DoD tab is highlighted when the issue status moves to an "In Progress" or "Done" category.

Sprint Gate

The Sprint Gate is a project-level page accessible from the left sidebar ("DoR / DoD"). It shows:

  • Sprint summary — overall readiness percentage, ready/partially ready/not ready counts
  • Per-issue breakdown — each issue with its DoR and DoD scores, sortable by readiness
  • Sprint selector — toggle between active sprint (summary uses DoD) and future sprint (summary uses DoR)

Use the Sprint Gate in sprint planning to ensure all issues meet readiness criteria before committing, and during the sprint to track completion against Definition of Done.

Project Settings

Each project has its own configuration. Go to Project Settings → "Definition of Ready/Done Settings" to:

  • Choose app mode — DoR only, DoD only, or Both
  • Toggle built-in rules — enable or disable each rule independently for DoR and DoD
  • Add custom criteria — create manual checkboxes or formula-based rules
  • Manage custom fields — the app auto-creates DoR Score, DoR Status, DoD Score, and DoD Status fields in Jira

DoR Built-in Rules

These rules evaluate whether an issue is ready to be worked on.

RuleCondition
Has DescriptionIssue description is at least 50 characters
Has Acceptance CriteriaDescription contains a bullet list, checklist, or keywords like "acceptance criteria", "given", "expected"
Has EstimateIssue has story points or a time estimate set
Has AssigneeIssue has an assignee
Has Epic / ParentIssue belongs to an epic or has a parent issue
Has LabelsAt least one label is assigned
Has ComponentAt least one component is assigned
Has Fix VersionAt least one fix version is set
Has Linked IssuesIssue has at least one linked issue

DoD Built-in Rules

These rules evaluate whether an issue meets the team's definition of done.

RuleCondition
Status Is DoneIssue status category is "Done"
All Subtasks DoneAll subtasks have status category "Done" (passes if no subtasks)
Has Test EvidenceDescription or comments contain phrases like "tested", "test result", "test evidence", "QA passed", "QA approved", "unit test", "integration test"
Has Code ReviewIssue has at least one linked issue (e.g. PR, review, dependency)
Has DocumentationDescription or comments contain phrases like "documentation", "documented", "docs updated", "readme updated", "wiki updated", "changelog updated", or labels include "documented" / "docs"
Has ResolutionIssue resolution is set
Has CommentIssue has at least one comment

Custom Criteria

Manual Checkboxes

Create criteria that team members check off manually on each issue. Useful for subjective checks that can't be automated:

Formula Criteria

Create rules that are automatically evaluated based on Jira field values. Each formula criterion consists of a field, an operator, and an optional comparison value.

labels contains "reviewed"storyPoints >= 1fixVersions not_emptypriority equals High

Formula Operators

OperatorExampleDescription
not_emptylabels not_emptyField has a value (non-empty string, non-empty array, number > 0)
emptyfixVersions emptyField is empty or zero
equalspriority equals HighExact match (case-insensitive)
not_equalsstatus not_equals DoneDoes not match
gt / gte / lt / ltestoryPoints gte 3Numeric comparison: greater than, greater or equal, less than, less or equal
containslabels contains reviewedSubstring match for strings; element match for arrays (case-insensitive)

Available fields: summary, description, assignee, priority, labels, components, fixVersions, issuelinks, storyPoints, timeEstimate, status, issueType.

Scoring & Field Sync

The readiness score is calculated as the percentage of passed criteria (built-in rules + custom criteria):

score = (passed criteria / total criteria) × 100
<50%

Not Ready

50–99%

Partially Ready

100%

Ready

Custom Field Sync

ReDo automatically creates and updates four custom Jira fields:

FieldTypeValues
DoR ScoreNumber0–100
DoR StatusSelectNot Ready / Partially Ready / Ready
DoD ScoreNumber0–100
DoD StatusSelectNot Done / Partially Done / Done

These fields update automatically whenever an issue is viewed in the panel and on every issue create/update event. You can use them in JQL queries, dashboards, and board filters.

App Modes

Each project can run in one of three modes, configurable in Project Settings:

DoR only

Evaluate Definition of Ready criteria only. Best for teams starting with quality gates on incoming issues.

DoD only

Evaluate Definition of Done criteria only. Best for teams focused on completion standards.

Both

Evaluate both DoR and DoD with separate tabs in the issue panel. Sprint Gate shows DoR for future sprints and DoD for active sprints.

Plans & Limits

FeatureFreePaid
Built-in rulesAllAll
Manual criteriaUp to 2Unlimited
Formula criteriaUp to 2Unlimited
Custom field syncYesYes
Sprint GateYesYes

Need help?

Contact us at hello@monteteam.com for any questions about setup, configuration, or feature requests.