Skip to content

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.

Paste it into your assistant. It tells you what it will send or change before it runs live.

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

  1. When a release is published, GitHub sends its version and notes to your automation's trigger link.

  2. ClickRuntime finds the Jira ticket keys mentioned in the notes.

  3. It creates a matching version in your Jira project, sets it on each ticket and moves them to Done.

  4. If you turn on AI, it rewrites the notes in plain language.

  5. 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

RunsThe moment it happens
Update Jira and post release notes to Slack when you tag a releasejust nowSucceeded
Slack · #releasesReleased v2.14.0 • ENG-402 Bulk export to CSV • ENG-417 Faster search for large workspaces

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.
  • 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

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.
release_and_commit_updates_in_jira_posted_to_slack.pyexample
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?
From Jira keys like ENG-123 in the release notes or commit messages. Teams that put the key in their commit or branch names get the best results.
Which status does it move tickets to?
The status you choose, such as Done or Released. It uses the matching transition in your Jira workflow.
Can it work with tags from other tools?
Yes. Anything that can send a web request with the version name and release notes can start it.
What permissions does it need?
Jira edit; Slack chat:write. Nothing else in your accounts is used.
Does it need AI?
No, but you can ask for an AI step (for example a summary). It then uses ClickRuntime's built-in AI allowance.
How many runs does it use?
One run for each event the app sends.
Can I change how it works?
Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

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.