Resolved late, days late and due date changes as Jira fields
JQL compares a field to a value, never to another field, and it cannot search due date history. So "resolved after its due date" and "due date pushed back" are not searchable in Jira (Atlassian closed the 676-vote request JRACLOUD-20727 as Won't Do). This Jira Cloud app keeps five read-only fields current so you can. Runs entirely inside Atlassian's infrastructure. No servers of ours, no analytics.
The five fields
| Field | Type | What it holds |
|---|---|---|
| Resolved late | Text | yes when the work item was completed after its due date, no when on time or early; empty while open or without a due date |
| Days late at resolution | Number | Completion date minus due date in days (negative means early) |
| Due date change count | Number | How many times an existing due date was changed or cleared |
| Original due date | Date | The first due date ever set on the work item |
| Due date slip (days) | Number | Current due date minus original due date in days (positive means pushed back) |
Completion date is the resolution date. On workflows that never set a resolution, it is the date the work item moved into a Done status.
What you can do with them
- Work finished late this month:
"Resolved late" = "yes" AND statusCategory = Done AND updated >= startOfMonth(). - Badly late work:
"Days late at resolution" > 3. - Due dates that keep moving:
"Due date change count" >= 2or"Due date slip (days)" > 7. - On-time rate: compare the counts of
"Resolved late" = "no"and"Resolved late" = "yes"in a dashboard. - Add any of the five as columns in list views and saved filters, show them in dashboards, and include them in CSV exports.
How it works
- On install, existing work items with a due date or a completion are backfilled in pages, without any automation rule or rule-run quota.
- When a work item's due date, resolution or status changes, its fields update within seconds.
- A nightly job repairs work items updated in the last two days, in case an event was missed.
- Built on Atlassian Forge with no external egress.
Good to know
- Jira creates app fields once the site has at least one company-managed project (space).
- The text field matches exactly: write
"Resolved late" = "yes", not~.
Pricing
Free for sites with up to 10 users. Above that, priced per user per month through the Atlassian Marketplace, with Atlassian's standard 30-day free evaluation. Billing, invoices, and cancellation are handled by Atlassian.
Permissions
read:jira-work to read due dates, completion dates, status category and the due date change history; write:app-data:jira to write its own five fields; storage:app for two small internal records. Details in the privacy notice.
Guide
JQL for overdue work and due dates: what Jira can do natively, and what it cannot.
Writing JQL for these fields?
Our free Jira Cloud JQL guides show working queries step by step, and the JQL Cookbook (ours, paid, pay what you want from $12) collects 66 copy-paste queries, each checked against Jira Cloud's strict parser.
Support
Email support@sidecartools.com. Replies within two business days.