Weekly
Compare Jira progress with monday.com goals weekly
Every Monday you get a report showing which epics are behind, comparing finished Jira work with the targets on your monday.com board.
- Runs
- Weekly
- Apps
- Jira, monday.com
- AI
- Not needed
- Access
- Jira read; monday.com read (+write for status)
Send this to your assistant
Create a ClickRuntime automation: every Monday at 9am, read the goals on my monday.com OKR board, check how many Jira issues are done in each linked epic, and email me which ones are behind schedule.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
Leadership tracks goals in monday.com while the actual work lives in Jira epics. Knowing whether a goal is on track means opening both tools and doing arithmetic, so it usually happens in a rush before a quarterly review.
Comparing the two automatically every week shows which goals are slipping while there is still time to act. The report is the same every Monday, so trends are easy to follow.
What you get out of it
Real progress, not opinions
Progress comes from finished Jira issues, not someone's estimate in a meeting.
Slipping goals flagged early
Epics behind where they should be at this point in the quarter are named, so you can act mid-quarter.
No manual cross-checking
Nobody opens two tools and a calculator every week; the numbers are pulled for you.
A consistent weekly view
The same report every Monday makes it easy to see whether things are improving.
How it works
What happens, step by step
Every Monday ClickRuntime reads the goals and their Jira epic keys from your monday.com board.
For each epic it counts how many Jira issues are done out of the total.
It compares that with how far through the quarter you are and flags epics that are behind.
The report is emailed to you.
Before it runs live
- Connect Jira
- Connect monday.com
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
- 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 and monday.com steps into one automation
Under the hood
The code that runs this automation
from datetime import date
from clickruntime import on_trigger, credentials, http, notify
BOARD = 1234567890
ITEMS = """query ($board: [ID!]) { boards(ids: $board) { items_page(limit: 200) { items {
id name url column_values { id text } } } } }"""
def monday(query, **variables):
resp = http.post("https://api.monday.com/v2", json={"query": query, "variables": variables},
headers={"Authorization": credentials.secret("MONDAY_API_TOKEN"), "API-Version": "2024-10"})
resp.raise_for_status()
return resp.json()["data"]
JIRA_URL = "https://api.atlassian.com/ex/jira/your-cloud-id/rest/api/3"
def jira(method, path, **kw):
resp = http.request(method, JIRA_URL + path, headers={"Authorization": "Bearer " + credentials.connection("jira", "work")}, **kw)
resp.raise_for_status()
return resp.json() if resp.content else None
def count(jql):
return jira("POST", "/search/approximate-count", json={"jql": jql})["count"]
@on_trigger
def run(event):
today = date.today()
expected = min((today - date(today.year, 3 * ((today.month - 1) // 3) + 1, 1)).days / 91, 1)
lines, behind = [], 0
for i in monday(ITEMS, board=[BOARD])["boards"][0]["items_page"]["items"]:
epic = {c["id"]: c["text"] for c in i["column_values"]}.get("epic")
if not epic:
continue
total = count(f'parent = "{epic}"')
done = count(f'parent = "{epic}" AND statusCategory = Done') / total if total else 0
flag = done < expected - 0.15
behind += flag
lines.append(f"{'⚠️ ' if flag else ''}{i['name']} ({epic}): {done:.0%} done, expected {expected:.0%}")
notify.email_me(f"Goal health: {behind} behind", "\n".join(lines) or "No goals with linked epics.")
return {"goals": len(lines), "behind": behind}FAQ
Common questions
How are goals linked to epics?
How is behind calculated?
Can it post to Slack instead?
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
Open Jira issues for approved monday.com requests
When a change request is approved on your monday.com board, a Jira issue is opened and its key is written back to the item.
See how it worksSync monday.com items to Jira without duplicates
New and updated monday.com items show up as Jira issues, and changes update the same issue instead of creating a new one.
See how it worksKnow the moment your website goes down
Your team hears in Slack when the site stops responding or slows down, and again when it's back.
See how it worksKeep exploring
Set up “Compare Jira progress with monday.com goals weekly” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.