On a schedule
Get a sprint report when a sprint closes
When a sprint ends you see the completion rate, what got done and what carried over, by person.
- Runs
- On a schedule
- Apps
- Jira
- AI
- Not needed
- Access
- read
Send this to your assistant
Create a ClickRuntime automation: when a sprint closes on the ABC board, email me the completion rate, the issues done by each person and the issues carried over.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A sprint ends, and the product owner is asked what shipped, what rolled over and who did the work. The Jira sprint report shows a chart, but turning it into a message for stakeholders means opening each issue, tallying points by person, and noting why items were carried over. The summary gets written late, from memory, and the items that slipped are described vaguely, which makes the next sprint's promises harder to trust.
On a schedule, ClickRuntime lists the sprints on your board, detects one that has newly closed, runs a JQL search for the issues in that sprint, and works out which were done and which were not. It emails a report showing completed work, carried-over items and the people responsible.
It helps scrum masters, product owners and engineering managers who share sprint results with others.
What you get out of it
Stakeholders get results the day a sprint ends
A report on the first morning after a sprint closes keeps stakeholders informed while the work is fresh. Delays in reporting make leadership feel the team is opaque, even when it is not.
Carried-over work is visible
Items that rolled to the next sprint are listed by name, so nothing disappears quietly. Seeing the same issue carried over three sprints in a row prompts a conversation about whether it is stuck.
Contributions are recorded fairly
Listing completed work by assignee shows who delivered what. That is useful for recognition, and for noticing when one person carried a heavy share of the sprint. It also shows when the same few people are carrying most of the load.
The retrospective starts with facts
With a list of what finished and what did not, the team can discuss why instead of arguing about what happened. Time in the meeting goes to improvement, not to recollection.
Commitments become more realistic
Comparing planned with delivered work over several sprints shows how much the team actually completes. Future commitments based on that history are more credible than ones based on optimism. That track record lets the product owner say yes or no to new requests with confidence.
How it works
What happens, step by step
Every hour, ClickRuntime checks your Jira board for a sprint that has just closed.
When it finds one, it collects every issue in that sprint.
It works out the completion rate, how many issues each person finished and what carried over.
The sprint report is emailed to you.
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
- Act only on the items that match your own rules, and skip the rest
- 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 collections import defaultdict
from clickruntime import on_trigger, credentials, http, state, notify, report_fetched
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):
sprints = jira("GET", f"/rest/agile/1.0/board/{BOARD_ID}/sprint", params={"state": "closed", "maxResults": 50})["values"]
reported = set(state.get("reported") or [])
new = [s for s in sprints if s["id"] not in reported]
report_fetched(len(new))
if not new:
return {"reported": 0}
for s in new:
if reported: # first run only records existing sprints
issues = search(f"sprint = {s['id']}", ["summary", "status", "assignee"], 300)
done = [i for i in issues if i["fields"]["status"]["statusCategory"]["key"] == "done"]
by_person = defaultdict(int)
for i in done:
by_person[(i["fields"].get("assignee") or {}).get("displayName", "Unassigned")] += 1
carried = [f" {i['key']} {i['fields']['summary']}" for i in issues if i not in done]
notify.email_me(f"{s['name']} closed: {len(done)}/{len(issues)} done",
f"Completion: {len(done) / max(len(issues), 1):.0%}\n\nDone by person:\n" +
"\n".join(f" {p}: {n}" for p, n in sorted(by_person.items())) +
"\n\nCarried over:\n" + ("\n".join(carried) or " none"))
reported.add(s["id"])
state.set("reported", sorted(reported))
return {"reported": len(new)}FAQ
Common questions
How does it know a sprint just closed?
Are story points included in the report?
Will the report work if we use Kanban instead of sprints?
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
Get pinged about Highest and Blocker issues
Within minutes of a top-priority issue being created, you get its summary, reporter and link.
See how it worksTriage new Jira tickets as they come in
New tickets get labels and a priority, and the reporter is asked for anything missing, like steps to reproduce.
See how it worksEmail release notes when a Jira version is released
When a version is released, you get readable release notes built from its resolved issues.
See how it worksKeep exploring
Set up “Get a sprint report when a sprint closes” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.