Skip to content

On a schedule

Email release notes when a Jira version is released

When a version is released, you get readable release notes built from its resolved issues.

Runs
On a schedule
Apps
Jira
AI
Yes, uses the built-in AI allowance
Access
read

Send this to your assistant

Create a ClickRuntime automation: when a version is released in project APP, write release notes from its resolved issues, grouped into features and fixes, and email them to me.

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

Developers write ticket titles for themselves: "Fix NPE in OrderMapper", "Bump retry limit". When a version is released in Jira, someone has to turn forty of those into release notes that customers or support staff can understand. That job falls to a product manager on release day, usually at the end of a long week, and the notes end up late, thin, or copied straight from ticket titles that mean nothing to a customer.

On a schedule, ClickRuntime lists the versions in your Jira project and notices any that have newly been marked released. It collects the issues with that fix version, has built-in AI group them into sections such as new features, improvements and bug fixes in plain language, and emails the notes to you.

Product managers, support teams and technical writers use it to get a solid first draft.

What you get out of it

  • Release day stops being a writing task

    The draft is waiting in your inbox when the release goes out. You edit and publish instead of starting from scratch, which turns an hour of effort into a few minutes of review.

  • Customers understand what changed

    Plain-language notes tell customers what is new and what was fixed, using words they know. That reduces confusion and support tickets about changes they did not expect after an update.

  • Support is briefed in advance

    Support agents see what shipped before customers ask. They can answer questions about new behavior confidently instead of finding out about a change from the customer. That avoids the awkward situation where a customer asks about a fix and the support team has not heard of it.

  • Nothing shipped goes unmentioned

    Because the notes come from the issues tagged with the version, small fixes are not forgotten. A complete list is more trustworthy than notes written from the memory of whoever wrote the code.

  • Consistent structure across releases

    Each release's notes follow the same grouping, so readers learn where to look. Sales and success teams find it easy to scan for new features without reading the whole thing.

How it works

What happens, step by step

  1. Every day, ClickRuntime checks your Jira project for versions that have just been released.

  2. For each new release, it collects the issues resolved in that version.

  3. AI writes readable release notes, grouped into features and fixes, with the issue keys.

  4. The notes are emailed to you.

Before it runs live

  • Connect Jira

What you get

RunsOn a schedule
Email release notes when a Jira version is releasedtoday, 9:00Succeeded
Email · Release notes: APP 3.8.0Features • Bulk edit for invoices (APP-912) Fixes • PDF totals rounding (APP-930)

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 Slack
  • Combine it with other Jira 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.
ai_release_notes_emailed.pyexample
from clickruntime import on_trigger, credentials, http, ai, state, notify, report_fetched

JIRA = "https://api.atlassian.com/ex/jira/your-cloud-id"

def jira(method, path, **kw):
    resp = http.request(method, JIRA + path, headers={
        "Authorization": f"Bearer {credentials.connection('jira', 'work')}", "Accept": "application/json"}, **kw)
    resp.raise_for_status()
    return resp.json() if resp.content else None

def search(jql, fields, limit=100):
    return jira("POST", "/rest/api/3/search/jql", json={"jql": jql, "fields": fields, "maxResults": limit})["issues"]


@on_trigger
def run(event):
    done = set(state.get("released") or [])
    versions = [v for v in jira("GET", "/rest/api/3/project/APP/versions") if v.get("released")]
    new = [v for v in versions if v["id"] not in done]
    report_fetched(len(new))
    if not new:
        return {"emailed": 0}
    for v in new:
        if state.get("released") is not None:
            issues = search(f'project = APP AND fixVersion = {v["id"]} AND statusCategory = Done', ["summary", "issuetype"], 200)
            lines = "\n".join(f"{i['key']} [{i['fields']['issuetype']['name']}] {i['fields']['summary']}" for i in issues)
            notes = ai.generate(lines[:12000] or "No issues", max_output_tokens=700,
                                system="Write short release notes grouped into Features and Fixes, one line per item.").text
            notify.email_me(f"Release notes: APP {v['name']}", notes)
        done.add(v["id"])
    state.set("released", sorted(done))
    return {"versions": [v["name"] for v in new]}

FAQ

Common questions

How does it decide an issue belongs to a release?
It uses Jira's fix version field. Every issue with the released version in that field is included. Issues that were never given a fix version will not appear, so make sure your team sets it during planning.
Are the notes safe to publish as they are?
Treat them as a draft. The AI describes what the tickets say, but it may include internal wording or details you do not want public. A quick review before publishing keeps internal names and unreleased plans out of customer-facing notes.
Does it work with several Jira projects?
Yes. It can watch the versions in one project or several and send a separate email per project. Tell your AI assistant which projects to cover, and whether each should go to a different recipient, such as the product owner for that area.
What permissions does it need?
read. Nothing else in your accounts is used.
Does it need AI?
Yes. It uses ClickRuntime's built-in AI, so you don't need an OpenAI or Anthropic key. Every plan includes a monthly AI allowance.
How many runs does it use?
One run each time it checks. Checks that find nothing new and stop right away aren't counted.
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 “Email release notes when a Jira version is released” from your assistant

Copy the prompt above, or connect your assistant first. Free plan, no credit card.