Skip to content

On a schedule

Turn vendor security advisories into Jira tickets

New security advisories from the vendors you rely on become Jira tickets, and you get an email for each one.

Runs
On a schedule
Apps
Gmail, Jira
AI
Not needed
Access
Jira create issues; gmail.send

Send this to your assistant

Create a ClickRuntime automation: every 6 hours, check the security advisory feeds for our vendors; for each new advisory, create a ticket in Jira project SEC and email 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

An IT manager at a mid-sized firm is responsible for patching a firewall, a VPN, a password manager and a dozen other products. Each vendor publishes advisories on its own site or feed, and checking them all is a weekly chore that slips during busy periods.

Turning every new advisory into a Jira ticket means each one is assessed and closed with a record. The email makes sure urgent ones are seen the same day, and the ticket history answers the auditor's question of how quickly advisories were handled.

What you get out of it

  • Every advisory is tracked

    Each one becomes a ticket with a link to the source. Nothing relies on someone checking vendor sites.

  • A record for audits

    Ticket dates show when each advisory arrived and when it was resolved. Compliance questions have clear answers.

  • No duplicates

    Advisories already ticketed are remembered. Each one appears once.

  • You hear the same day

    An email for each new advisory means urgent patches are not left until the next weekly check.

How it works

What happens, step by step

  1. Every few hours, ClickRuntime reads the advisory feeds from your vendors.

  2. It skips advisories it has already seen, and on the first run simply notes what is there.

  3. For each new advisory, it creates a ticket in your Jira security project with the title, date and link.

  4. You get an email listing the new tickets.

Before it runs live

  • Connect Google through your own Google app (a one-time, 10-minute setup), so it works with your own Gmail
  • Connect Jira

What you get

RunsOn a schedule
Turn vendor security advisories into Jira ticketstoday, 9:00Succeeded
Email · 1 new security advisoriesSEC-142 Critical: Remote code execution in VPN gateway firmware 7.2

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
  • 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 Gmail and 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.
security_advisories_turned_into_jira_tickets_and_emails.pyexample
import feedparser
from clickruntime import on_trigger, credentials, http, notify, state, report_fetched

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)

FEEDS = ["https://vendor-one.example/security/rss", "https://vendor-two.example/advisories.atom"]

@on_trigger
def run(event):
    seen = state.get("seen")
    entries = [e for url in FEEDS for e in feedparser.parse(http.get(url).content).entries]
    new = [e for e in entries if seen is not None and e.link not in seen]
    report_fetched(len(new))
    if not new and seen is not None:
        return {"new": 0}
    created = []
    for e in new:
        t = jira("POST", "/rest/api/3/issue", json={"fields": {"project": {"key": "SEC"}, "issuetype": {"name": "Task"},
                 "summary": f"Advisory: {e.title}"[:250], "labels": ["vendor-advisory"], "description": adf(f"{e.get('published', '')}\n{e.link}")}})
        created.append(f"{t['key']} {e.title}")
    if created:
        notify.email_me(f"{len(created)} new security advisories", "\n".join(created))
    state.set("seen", sorted({e.link for e in entries} | set(seen or [])))
    return {"new": len(created)}

FAQ

Common questions

Which advisory sources does it support?
Any that publish an RSS or Atom feed, which most large vendors do. You give it the list of feed addresses.
Can it filter to the products we use?
Yes. Give it keywords for your products, such as the model of your firewall, and other advisories are skipped.
Does the first run create tickets for old advisories?
No. The first run records what is already in each feed, and only advisories published after that become tickets.
What permissions does it need?
Jira create issues; gmail.send. Nothing else in your accounts is used.
Does it need AI?
No. It runs without AI, so it doesn't use your plan's 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 “Turn vendor security advisories into Jira tickets” from your assistant

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