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.
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
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.
It counts open tickets per assignee.
The figures are added as a new row in your Jira metrics sheet.
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
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
- 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
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?
What does the summary contain?
Can it track several projects?
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
Check a list of domains from a sheet and open Jira tickets for problems
Each day every domain in your sheet is checked, the status columns are updated, and each new problem opens one Jira ticket.
See how it worksCreate Jira onboarding tickets from a new-hire sheet
When HR adds a new hire to the sheet, Jira tickets for their accounts and equipment are created and the ticket keys appear in the row.
See how it worksTurn sheet rows into Jira tickets
Requests added to your sheet become Jira tickets within minutes, with the ticket key written back into the row.
See how it worksKeep exploring
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.