On a schedule
Escalate overdue Jira tasks with a Telegram alert
Each morning overdue Jira tasks are raised to high priority and the manager gets one Telegram message listing them.
- Runs
- On a schedule
- Apps
- Jira, Telegram
- AI
- Not needed
- Access
- Jira read+write; bot token
Send this to your assistant
Create a ClickRuntime automation: every weekday morning, find overdue tasks in Jira project OPS, raise them to High priority, and send the list to the manager on Telegram. Don't repeat a task two days running.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A field operations manager spends most of the day away from a desk. Overdue tasks pile up in Jira unseen, and by the time the manager checks the board on Friday, a customer has already complained.
Raising overdue tasks to high priority and sending a short Telegram list each morning reaches the manager wherever they are. They can call the right person straight away instead of discovering the problem days later.
What you get out of it
Managers hear on the move
Telegram reaches the manager's phone. No need to be at a desk to know what slipped.
Priority reflects reality
Overdue tasks move to high priority, so they rise to the top of everyone's view in Jira.
One message, not many
All overdue tasks arrive in a single list each morning. Easy to scan between jobs.
No repeated nagging
Tasks already escalated yesterday are left out of today's list. Every message has something new.
How it works
What happens, step by step
Every weekday morning, ClickRuntime finds tasks in your Jira project that are past their due date and not done.
It leaves out tasks it escalated yesterday, which it remembers.
Each remaining task is raised to high priority.
The manager gets one Telegram message listing the tasks, their assignees and due dates.
Before it runs live
- Connect Jira
- Connect Telegram
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 Telegram steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_trigger, credentials, http, state
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)
CHAT_ID = "123456789"
def telegram(text, chat_id=CHAT_ID):
http.post(f"https://api.telegram.org/bot{credentials.secret('TELEGRAM_BOT_TOKEN')}/sendMessage", json={"chat_id": chat_id, "text": text}).raise_for_status()
@on_trigger
def run(event):
issues = jira("POST", "/rest/api/3/search/jql", json={"jql": "project = OPS AND duedate < now() AND statusCategory != Done ORDER BY duedate",
"fields": ["summary", "duedate", "assignee", "priority"], "maxResults": 100})["issues"]
yesterday = set(state.get("escalated") or [])
new = [i for i in issues if i["key"] not in yesterday]
for i in new:
if i["fields"]["priority"]["name"] not in ("High", "Highest"):
jira("PUT", f"/rest/api/3/issue/{i['key']}", json={"fields": {"priority": {"name": "High"}}})
if new:
telegram("⏰ Overdue tasks\n" + "\n".join(f"{i['key']} {i['fields']['summary']} ({(i['fields']['assignee'] or {}).get('displayName', 'unassigned')}, "
f"due {i['fields']['duedate']})" for i in new))
state.set("escalated", [i["key"] for i in issues])
return {"overdue": len(issues), "escalated": len(new)}FAQ
Common questions
Does it change anything else on the ticket?
Can different teams go to different managers?
Can it also email me?
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 and ping Telegram for provider incidents
When a service you depend on reports a new incident on its status page, a Jira issue is opened and your team gets a Telegram message.
See how it worksCreate Jira tickets from Telegram messages
Staff message an IT problem to your Telegram bot, a structured Jira ticket is created, and the bot replies with the ticket number.
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 “Escalate overdue Jira tasks with a Telegram alert” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.