Skip to content

On a schedule

Log daily Jira metrics to a sheet

Each day a row in your sheet records tickets created, resolved, open, stale and the load per person, with an optional summary by email.

Runs
On a schedule
Apps
Google Sheets, Jira
AI
Optional
Access
Jira browse; Sheets write

Send this to your assistant

Create a ClickRuntime automation: every evening, count tickets created, resolved, still open and not updated for 14 days in Jira project ENG, plus open tickets per assignee, add a row to my Jira metrics sheet, and email me a short summary.

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

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

Why use it

Why teams use this automation

A head of engineering wants to know whether the backlog is growing, who is overloaded and how many tickets go stale, but Jira's built-in reports are hard to share and do not keep history in a way leadership can chart.

A daily row of key numbers in a Google Sheet builds a history anyone can chart and share. Trends become obvious over weeks, and conversations about workload start from data rather than impressions.

What you get out of it

  • History you can chart

    A row per day builds a time series. Backlog growth and throughput become easy to see.

  • Workload is visible

    Open tickets per person show who is stretched. Work can be rebalanced before people burn out.

  • Stale tickets are counted

    The number of tickets not updated for two weeks shows how healthy the backlog is.

  • Shareable with leadership

    A Google Sheet is easy to share and chart. No Jira licence is needed to read it.

How it works

What happens, step by step

  1. Every evening, ClickRuntime counts the tickets in your Jira project that were created, resolved, are still open, and have not been updated for 14 days.

  2. It counts open tickets per assignee.

  3. The figures are added as a new row in your Jira metrics sheet.

  4. If you turn on AI, a short summary is emailed to you.

Before it runs live

  • Connect your Google Sheets account and pick the spreadsheets it may use
  • Connect Jira

What you get

RunsOn a schedule
Log daily Jira metrics to a sheettoday, 9:00Succeeded
Google Sheets · Jira metrics2026-10-17 | 9 created | 12 resolved | 184 open | 41 stale | Alex: 14, Sam: 11

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 Google Sheets and 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_and_weekly_jira_reports_logged_to_sheets.pyexample
from collections import Counter
from datetime import date
from google.oauth2.credentials import Credentials
from googleapiclient.discovery import build
from clickruntime import on_trigger, credentials, http, notify, ai

JIRA, SITE = "https://api.atlassian.com/ex/jira/your-cloud-id", "https://acme.atlassian.net/browse/"
adf = lambda text: {"type": "doc", "version": 1, "content": [{"type": "paragraph", "content": [{"type": "text", "text": text}]}]}

def jira(method, path, **kw):
    resp = http.request(method, JIRA + path, headers={"Authorization": f"Bearer {credentials.connection('jira', 'work')}", "Accept": "application/json"}, **kw)
    return resp.raise_for_status() or (resp.json() if resp.content else None)

SHEET_ID, P = "your-spreadsheet-id", "project = ENG"

def search(jql, fields=("assignee",)):
    return jira("POST", "/rest/api/3/search/jql", json={"jql": jql, "fields": list(fields), "maxResults": 500})["issues"]

@on_trigger
def run(event):
    created = len(search(f"{P} AND created >= startOfDay()"))
    resolved = len(search(f"{P} AND resolved >= startOfDay()"))
    open_issues = search(f"{P} AND statusCategory != Done")
    stale = len(search(f"{P} AND statusCategory != Done AND updated <= -14d"))
    load = Counter((i["fields"]["assignee"] or {}).get("displayName", "Unassigned") for i in open_issues)
    row = [str(date.today()), created, resolved, len(open_issues), stale, ", ".join(f"{n}: {c}" for n, c in load.most_common())]
    values = build("sheets", "v4", credentials=Credentials(credentials.connection("google", "work")), cache_discovery=False).spreadsheets().values()
    values.append(spreadsheetId=SHEET_ID, range="Jira metrics!A:F", valueInputOption="USER_ENTERED", body={"values": [row]}).execute()
    try:
        notify.email_me(f"Jira {date.today()}: {created} created, {resolved} resolved",
                        ai.generate(str(row), system="Summarise these Jira metrics in 2 plain sentences for a manager.", max_output_tokens=100).text)
    except (ai.AINotIncluded, ai.AILimitReached):
        pass
    return {"row": row}

FAQ

Common questions

Can it run weekly instead?
Yes. A weekly run adds one row per week with the same figures for the whole week.
What does the summary contain?
A few sentences on the day's numbers compared with the previous row, written by AI if you turn it on. It is optional.
Can it track several projects?
Yes. Name the projects and each gets its own row, or its own tab.
What permissions does it need?
Jira browse; Sheets write. Nothing else in your accounts is used.
Does it need AI?
No, but you can ask for an AI step (for example a summary). It then uses ClickRuntime's built-in 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.

Set up “Log daily Jira metrics to a sheet” from your assistant

Copy the prompt above, or connect your assistant first. Free plan, no credit card.