Every 10 minutes
Turn sheet rows into Jira tickets
Requests added to your sheet become Jira tickets within minutes, with the ticket key written back into the row.
- Runs
- Every 10 minutes
- Apps
- Google Sheets, Jira
- AI
- Not needed
- Access
- Sheets read+write; Jira create issues
Send this to your assistant
Create a ClickRuntime automation: every 10 minutes, check my Requests sheet for rows without a ticket key, create a Jira ticket in OPS for each, write the key back, and email me a list.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
An account management team logs client escalations in a shared sheet because it is quick and everyone has access. The operations team works from Jira, so escalations are copied across by hand, sometimes days later.
Creating a ticket for each new row, and writing the key back, lets account managers keep their sheet while operations gets a proper queue. Everyone can see that a request was picked up, and nothing waits for a manual copy.
What you get out of it
Keep the sheet people like
Requesters keep using a simple spreadsheet. No new tool to learn.
Operations works in Jira
Every request is a ticket with a priority and description. It fits the team's normal process.
Keys show what was picked up
The ticket key in the row confirms the request is in the queue. Requesters can look it up.
No copy-and-paste delays
Tickets are created within minutes of a row being added. Urgent escalations are not held up.
How it works
What happens, step by step
Every 10 minutes, ClickRuntime reads your Requests sheet.
It finds rows with a summary but no ticket key.
A Jira ticket is created for each, with the summary, description and priority from the row.
The ticket key is written back into the row, so it is not created twice.
You get an email listing the new tickets.
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
- 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 Google Sheets and Jira steps into one automation
Under the hood
The code that runs this automation
from google.oauth2.credentials import Credentials
from googleapiclient.discovery import build
from clickruntime import on_trigger, credentials, http, notify, report_fetched
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 = "your-spreadsheet-id"
@on_trigger
def run(event):
values = build("sheets", "v4", credentials=Credentials(credentials.connection("google", "work")), cache_discovery=False).spreadsheets().values()
rows = values.get(spreadsheetId=SHEET_ID, range="Requests!A2:D").execute().get("values", [])
todo = [(i, r + [""] * (4 - len(r))) for i, r in enumerate(rows, start=2) if r and r[0] and (len(r) < 4 or not r[3])]
report_fetched(len(todo))
if not todo:
return {"created": 0}
created = []
for i, (summary, description, priority, _) in todo:
key = jira("POST", "/rest/api/3/issue", json={"fields": {"project": {"key": "OPS"}, "issuetype": {"name": "Task"}, "summary": summary[:250],
"priority": {"name": priority or "Medium"}, "description": adf(description or summary)}})["key"]
values.update(spreadsheetId=SHEET_ID, range=f"Requests!D{i}", valueInputOption="RAW", body={"values": [[key]]}).execute()
created.append(f"{key} {summary}")
notify.email_me(f"{len(created)} requests sent to Jira", "\n".join(created))
return {"created": len(created)}FAQ
Common questions
Which columns does it read?
What if a row is incomplete?
Does it update the sheet when the ticket is closed?
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
Create 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 worksCheck 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 worksLog 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.
See how it worksKeep exploring
Set up “Turn sheet rows into Jira tickets” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.