The moment it happens
Update Jira and post release notes to Slack when you tag a release
When a release is tagged, the Jira tickets mentioned in its commits get a fix version and move to Done, and Slack gets the release notes.
- Runs
- The moment it happens
- Apps
- Jira, Slack
- AI
- Optional
- Access
- Jira edit; Slack chat:write
Send this to your assistant
Create a ClickRuntime automation: when a release is published on GitHub, find the Jira keys in its notes, create a version in ENG, set it on those tickets and move them to Done, then post release notes to #releases.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
After each release, a team lead spends half an hour updating Jira: creating the version, setting it on each ticket, moving tickets to Done, then writing a note for QA and support. On busy weeks it is skipped, and Jira no longer shows what shipped when.
Doing all of that the moment a release is tagged keeps Jira accurate without the chore. QA and support see exactly which tickets are in the release, in a channel they read.
What you get out of it
Jira shows what shipped
Every ticket in the release gets its fix version and moves to Done. Release history in Jira is complete.
No release-day admin
The version, the ticket updates and the announcement happen together, automatically.
QA and support know what changed
Release notes in Slack list the tickets with links. Testers know what to check and support knows what to tell customers.
Readable notes
With AI turned on, the notes are rewritten in plain language. People outside engineering can follow them.
How it works
What happens, step by step
When a release is published, GitHub sends its version and notes to your automation's trigger link.
ClickRuntime finds the Jira ticket keys mentioned in the notes.
It creates a matching version in your Jira project, sets it on each ticket and moves them to Done.
If you turn on AI, it rewrites the notes in plain language.
The release notes are posted to your #releases Slack channel with links to each ticket.
Before it runs live
- Connect Jira
- Connect Slack, then invite the app to the channel (type /invite @ClickRuntime there)
- Paste your automation's link into the other app's webhook settings
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
- Change what the AI looks for, or how it writes the result
- Add another app, for example also send it to Google Sheets
- Combine it with other Jira and Slack steps into one automation
Under the hood
The code that runs this automation
import re
from clickruntime import on_event, 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)
PROJECT, DONE = "ENG", "Done"
@on_event
def handle(event):
rel = (event.json or {}).get("release") or {}
keys = sorted(set(re.findall(rf"{PROJECT}-\d+", rel.get("body") or "")))
if not keys:
return {"tickets": 0}
project_id = jira("GET", f"/rest/api/3/project/{PROJECT}")["id"]
version = jira("POST", "/rest/api/3/version", json={"name": rel["tag_name"], "projectId": project_id, "released": True})
titles = []
for key in keys:
jira("PUT", f"/rest/api/3/issue/{key}", json={"update": {"fixVersions": [{"add": {"id": version["id"]}}]}})
moves = jira("GET", f"/rest/api/3/issue/{key}/transitions")["transitions"]
done = next((t for t in moves if t["to"]["name"] == DONE), None)
if done:
jira("POST", f"/rest/api/3/issue/{key}/transitions", json={"transition": {"id": done["id"]}})
titles.append(f"• <{SITE}{key}|{key}> {jira('GET', f'/rest/api/3/issue/{key}?fields=summary')['fields']['summary']}")
notes = "\n".join(titles)
try:
notes = ai.generate(notes, system="Rewrite as short plain-language release notes, keeping the ticket links.", max_output_tokens=500).text
except (ai.AINotIncluded, ai.AILimitReached):
pass
notify.slack(f"Released {rel['tag_name']}\n{notes}", channel="#releases")
return {"version": rel["tag_name"], "tickets": keys}FAQ
Common questions
How does it find the tickets?
Which status does it move tickets to?
Can it work with tags from other tools?
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
Alert Slack on production errors with one Jira bug per error
Production errors are posted to Slack straight away, and each distinct error opens exactly one Jira bug, with repeats added as comments.
See how it worksTriage support requests into Jira and alert the right Slack channel
Each incoming support request becomes a Jira ticket with a category, priority and summary, and is posted to the Slack channel for that category.
See how it worksTurn security alerts into Jira tickets and Slack messages
Each security alert creates one Jira ticket, posts to your security channel, and messages the affected person in Slack when the alert names them.
See how it worksKeep exploring
Set up “Update Jira and post release notes to Slack when you tag a release” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.