Move Unfinished Jira Tickets to Next Sprint
For the last hour of the sprint. DuckyHelper learns Jira's web API once, finds every unfinished ticket, adds a short note on why it slipped, and moves them all to the next sprint at once instead of dragging them one by one.
“Move all unfinished tickets in the current Jira sprint to the next one, with a note on why each slipped.”
- 01Write small tools for Jira, onceSmall JavaScript tools made from how Jira already works. The next run calls them directly.
searchIssues(jql)addComment(id, text)moveToSprint(ids, sprint)
- 02Find unfinished tickets in this sprint
- 03Note why each one slipped
- 04Move them all to next sprint in one call
- 05Draft a summary for the team
You getA clean start to the next sprint. Every carryover moved and explained. Next sprint, it's one ask.
A run, drawn from this page · early access on Mac
It's built to wait for your OK.
It does the work, then stops with the Slack post ready for you. You see exactly what it wrote, then Send, Edit or Deny.
If it hits a sign-in, you sign in yourself. It's built not to type your passwords or card numbers.
SlackSlack postNeeds your OKDo it once. Then let it repeat.
When it's done, it offers to keep doing it: every Monday at 9:00 AM. Each run goes through the API it learned the first time, so it's quick, and it's still built to ask before it sends or pays.
Always-on automations are in early access on Mac.
Before you ask it.
What do I say?
Press fn (Ctrl+Shift+Space on Windows and Linux) and ask out loud, in your own words, like "Move all unfinished tickets in the current Jira sprint to the next one, with a note on why each slipped."
Why is the second time faster?
The first time, it writes small JavaScript tools for Jira and Slack and builds an API from each site's own buttons, forms and requests. After that it calls them directly, so the job runs in one go instead of click by click. It costs less and breaks less.
Will it send anything without me?
It's built to ask first before it sends a message or pays for anything, and to wait for your yes. It may not recognize every send or payment, so keep an eye on tasks that involve messages or money. It's built not to type your passwords or card numbers: you sign in yourself, and it picks up from there.
Why not just do it by hand?
Closing a sprint means dragging each open ticket over, and nobody records why it slipped.
Can it keep doing this on its own?
Yes. When it's done it offers to make it automatic (every Monday at 9:00 AM). Each run goes the same way and is still built to ask before it sends or pays.
Can I use this today?
Doing jobs in your apps is in early access on Mac. Talking to DuckyHelper, and having it see your screen and draw on it, works today on Mac, Windows and Linux.
- Early access
“Deploy the latest commit on main to production and tell me when it's live.”
Ship the Latest Commit and Watch the Build
See it run
- Early access
“Signups are failing in production. Check the Vercel logs, reproduce it, and open a PR with a fix.”
Debug a Vercel App From Logs to Fix
See it run
- Early access
“Check my Supabase project's health: schema, row security and anything that looks off.”
Check Your Supabase Database Is Healthy
See it run
Do anything
Ask it a question or hand it a job, in any app.
Doing jobs for you is in early access on Mac. Asking works on Mac, Windows and Linux.