-
-
Ticket panel: likely to slip, 3% of similar work finished in time, realistic date Tue 24 Nov
-
One click sets the realistic date: now on track at 83%, with Undo
-
Rovo agent Due Date Coach: can we finish this by 4 December?
-
Due Date Coach lists the open work likely to slip, each with a realistic finish
-
Which work slips: Legal is on time 35%, promised 4 days, takes 5
-
Project page: 64% of due dates met, open tickets ranked by chance
Inspiration
Every team sets due dates, and most of them are guesses. On our demo workspace the team met only 64% of its due dates (122 of 190), and nobody saw the misses coming. The answer was already in Jira: how long the same kind of work took last time. Nothing put that next to the date at the moment it was set. Legal, marketing, design and operations teams feel this most, because the agile forecasting tools are built for story points and sprints, not for a contract review due on Friday.
What it does
- Ticket panel. Opens on any ticket with a due date and says on track, tight or likely to slip. It gives the realistic date (the date 7 in 10 similar tickets made) and the share of similar work that finished in time, and it lists the past tickets behind every number. One button sets the realistic date. It asks first, because everyone watching sees the change, and it has Undo.
- Project page. How often the project keeps its dates, overall and month by month; which kinds of work slip and by how much (what people promise versus what it really takes); and every open ticket ranked by its chance of landing.
- Rovo agent, Due Date Coach. Ask "can we finish this by 4 December?" or "which of our open work is likely to slip?". It calls two actions and only states numbers they return, naming the tickets so anyone can check.
How we built it
- Atlassian Forge (Node 24), eligible for Runs on Atlassian: no egress, nothing leaves Atlassian.
- Modules:
jira:issuePanelandjira:projectPageshare one Custom UI bundle (Vite + React 18, Atlassian design tokens);rovo:agentwith two actions,check-due-dateandproject-due-date-health. - Every Jira read uses
asUser(), so the app only sees what the viewer can see. The only write is the due date, and only after the user confirms. - The engine is plain statistics, no machine learning: it reads the project's 500 most recent finished tickets, finds the closest matches (same type, same component, similar words in the title), measures working days from start to done and how often they met their own date, and gives a percentile date and a chance. If a ticket is already under way, only past tickets that ran at least as long count. 18 tests cover the engine.
- Demo data: 202 backdated requests across Legal, Design, Content, Web and Events, generated by a seeded script and imported with Jira's CSV importer.
Challenges we ran into
- Backdated history. Real created, resolved and due dates are what make the numbers honest, so the demo data had to survive Jira's CSV import with its original dates.
- Keeping Undo through Jira's own reload. After a due date changes, Jira refreshes the panel, which would wipe the Undo button. The panel remembers the last change for five minutes so Undo survives.
- Making Rovo trustworthy. The agent never computes anything itself: the numbers come from the actions, and the prompt forbids inventing tickets, dates or percentages.
Accomplishments that we're proud of
- It needs no setup, no estimates and no story points. Open a ticket and the answer is there.
- Every number links to the tickets behind it, so a manager can check it in one click.
- It is useful to teams that never use sprints: legal, marketing, events, operations.
What we learned
People trust a date when they can see the tickets it came from. "7 in 10 similar tickets took 6 working days" changes a conversation faster than any score.
What's next for Due Date Check
A weekly digest of dates at risk for each team lead, Confluence support for project plans, and suggesting a realistic date the moment a ticket is created.
Try it
- Install on Jira Cloud: https://due-date-check.vercel.app/#install
- Site: https://due-date-check.vercel.app
- Code: https://github.com/0xvikram/due-date-check
Built With
- forge
- javascript
- jira
- node.js
- react
- rovo
- vite