Daily
Get reminded about overdue or missing sprints
You're warned when a sprint is past its end date but still open, or when no sprint is active.
- Runs
- Daily
- Apps
- Jira
- AI
- Not needed
- Access
- read
Send this to your assistant
Create a ClickRuntime automation: each weekday at 8am, check the ABC board and email me if the active sprint is past its end date or if no sprint is active.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A Scrum team finishes a sprint on Friday and everyone goes home. On Monday nobody has closed it, so the sprint still shows as active with its end date in the past, and nobody started the next one. Work continues without a sprint, reports show a sprint with a hundred percent of its time elapsed, and the velocity chart skips a week. The team spends part of Tuesday's planning cleaning up what should have happened on Friday afternoon.
Each day, ClickRuntime reads the active and future sprints on your Jira board and compares each end date with today. If a sprint's end date has passed and it is still open, or if there is no active sprint at all, it emails you a reminder with the sprint names and dates.
Scrum masters and delivery managers who run several boards, and who cannot check each one daily, will find it a useful safety net.
What you get out of it
Velocity data stays accurate
Closing a sprint on time ensures completed points are counted in the right period. Late closures distort velocity, and every forecast built from that history becomes less reliable. Reports to leadership then show the true pace of the team.
Planning starts on schedule
When the reminder arrives the morning after a sprint should end, the team can close it and start the next one right away. Planning does not slip into the middle of the week.
No sprint-less stretches
Work done between sprints is untracked, so burndown charts and commitments are incomplete. A warning when no sprint is active means the gap gets noticed in a day, not at the end of the month.
Several boards, one reminder
A scrum master who looks after four teams cannot check each board every day. A single email listing boards with overdue or missing sprints replaces a daily tour through Jira.
Stakeholder reports remain meaningful
Dashboards and sprint reports sent to leadership rely on sprint dates being correct. Fixing lapses promptly prevents reports that show a sprint running three weeks over its length. Sprint reviews with clients also stay credible because the dates match what actually happened.
How it works
What happens, step by step
Every day, ClickRuntime looks at the active and upcoming sprints on your Jira board.
It compares each active sprint's end date with today's date.
If a sprint is past its end date but still open, or no sprint is running at all, it notes the problem.
You get a short email naming the sprint and the date it should have ended, so you can close it or start the next one.
Before it runs live
- Connect Jira
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Run it at a different time, more or less often, or only on weekdays
- Add an AI step, for example to summarize, sort or draft a reply
- Add another app, for example also send it to Slack
- Combine it with other Jira steps into one automation
Under the hood
The code that runs this automation
from datetime import datetime, timezone
from clickruntime import on_trigger, credentials, http, notify
JIRA = "https://api.atlassian.com/ex/jira/your-cloud-id"
def jira(method, path, **kw):
resp = http.request(method, JIRA + path, headers={
"Authorization": f"Bearer {credentials.connection('jira', 'work')}", "Accept": "application/json"}, **kw)
resp.raise_for_status()
return resp.json() if resp.content else None
def search(jql, fields, limit=100):
return jira("POST", "/rest/api/3/search/jql", json={"jql": jql, "fields": fields, "maxResults": limit})["issues"]
BOARD_ID = 12 # the ABC board
@on_trigger
def run(event):
active = jira("GET", f"/rest/agile/1.0/board/{BOARD_ID}/sprint", params={"state": "active"})["values"]
if not active:
notify.email_me("No active sprint on ABC", "The ABC board has no active sprint. Start the next one?")
return {"status": "none_active"}
now = datetime.now(timezone.utc)
overdue = [s for s in active if s.get("endDate") and datetime.fromisoformat(s["endDate"].replace("Z", "+00:00")) < now]
if overdue:
notify.email_me("ABC sprint past its end date", "\n".join(
f"{s['name']} ended {s['endDate'][:10]} but is still open." for s in overdue))
return {"status": "overdue" if overdue else "ok"}FAQ
Common questions
Which boards does it check?
Will it remind me if a sprint is only one day late?
Does it close or start the sprint for me?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Find open issues missing key details
Each morning you get a list of open issues with no assignee, estimate or priority.
See how it worksTrack created vs resolved issues each week
Each Monday you see how many issues were created and resolved last week, and how that compares with the week before.
See how it worksFind issues stuck in progress
Each morning you see issues that have sat In Progress for too long, grouped by assignee.
See how it worksKeep exploring
Set up “Get reminded about overdue or missing sprints” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.