On a schedule

Get a daily summary of what changed in Jira

Every weekday evening you get a short summary of the issues updated in your project that day, grouped by status.

Runs: On a schedule
Apps: Jira
AI: Yes, uses the built-in AI allowance
Access: read (Browse projects)

Send this to your assistant

Create a ClickRuntime automation: every weekday at 6pm, summarise the issues updated today in project ABC, grouped by status, and email me the summary.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

A project manager finishes her day and cannot say what actually happened in the project. Fifteen issues changed status, three comments carried decisions, and someone reopened a ticket that was supposed to be done. Reading the activity stream takes half an hour, so she skips it, and learns about the blocked deployment at the next morning's stand-up, when it has already cost a day. The summary replaces that scroll.

Every evening, ClickRuntime searches the project for issues updated since the start of the day, passes the changes to built-in AI, and emails you a summary organized by status. You see what moved, what was completed and what appears stuck, in a couple of minutes of reading.

Project managers, engineering managers and stakeholders who need to follow a project without living in Jira will like it.

What you get out of it

Blockers surface the same day
A problem noted in a comment, or a ticket that went back to In Progress, is called out in the summary. You can step in that evening instead of finding out at the next meeting.
Stand-ups start informed
When everyone has read the previous day's summary, the stand-up can focus on problems instead of status reading. Meetings shrink, and people can talk about what they need rather than what they did.
Remote teams stay in sync
Colleagues in other time zones can read what happened while they were offline. They start their day knowing what changed, rather than scrolling through notifications to catch up. Delays and reopened tickets are called out clearly, so you can raise the issue with the right person the same evening.
Stakeholders get a plain view
Executives and clients can follow progress through a readable summary without Jira access or training. It reduces ad hoc requests for updates that interrupt developers. Updates can be shared with clients and executives without giving each of them a Jira login or a tutorial.
Decisions buried in comments are noticed
Important choices are often made in an issue comment and never repeated elsewhere. Summaries that pick up those decisions help the rest of the team hear about them. Colleagues who were not in that thread hear about the outcome without having to scroll through every issue.

How it works

What happens, step by step

Every weekday at 6 pm, the automation collects the issues updated today in your Jira project.
AI writes a short summary of the day, grouped by status, such as Done and In Progress.
The summary is emailed to you with the number of issues updated.

Before it runs live

Connect Jira

What you get

RunsOn a schedule

Get a daily summary of what changed in Jiratoday, 9:00Succeeded

Email · Jira ABC today: 17 issues updatedDone • Checkout timeout fix shipped (ABC-341) In Progress • Search reindex 60% through, blocked on a schema review

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

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
Change what the AI looks for, or how it writes the result
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

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

daily_ai_summary_of_jira_activity.pyexample

from clickruntime import on_trigger, credentials, http, ai, 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"]


@on_trigger
def run(event):
    issues = search("project = ABC AND updated >= startOfDay() ORDER BY status", ["summary", "status", "assignee"], 200)
    if not issues:
        notify.email_me("Jira ABC today: no updates", "No issues in ABC were updated today.")
        return {"issues": 0}
    lines = "\n".join(f"{i['key']} | {i['fields']['status']['name']} | {(i['fields'].get('assignee') or {}).get('displayName', 'unassigned')} | "
                      f"{i['fields']['summary']}" for i in issues)
    summary = ai.generate(lines[:12000], max_output_tokens=600,
                          system="Summarise today's activity on these Jira issues, grouped by status, in short bullet points.").text
    notify.email_me(f"Jira ABC today: {len(issues)} issues updated", summary)
    return {"issues": len(issues)}

FAQ

Common questions

Which project does the summary cover?

It covers the project you name in the search, such as ABC, and you can include several projects or limit it to a board, component or label. Each version can be sent to a different person who cares about that area.

How does it know what changed today?

It uses Jira's updated date to find issues touched since the start of the day, then reads their current status and recent comments. It describes what it can see and does not know about changes made outside Jira.

Can I send the summary to a Slack channel as well?

Yes. Besides email, the summary can be posted to a team channel in Slack at the same time, which suits teams that prefer not to use inboxes. Tell your AI assistant the channel and the time you want it sent.

What permissions does it need?

read (Browse projects). Nothing else in your accounts is used.

Does it need AI?

Yes. It uses ClickRuntime's built-in AI, so you don't need an OpenAI or Anthropic key. Every plan includes a monthly AI allowance.

How many runs does it use?

One run each time it runs (on a schedule). Checks that find nothing to do and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

On a schedule