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.
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
Every few hours, ClickRuntime reads the advisory feeds from your vendors.
It skips advisories it has already seen, and on the first run simply notes what is there.
For each new advisory, it creates a ticket in your Jira security project with the title, date and link.
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
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
- 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
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?
Can it filter to the products we use?
Does the first run create tickets for old advisories?
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
Email customers when the bug they reported is fixed
When a Jira bug is resolved, the customers who reported it get a short email from you saying it is fixed.
See how it worksTurn support emails into categorised Jira tickets
Every email to your support address becomes a Jira ticket with a category, priority and summary, and the sender gets an acknowledgement with the ticket number.
See how it worksCreate Jira onboarding tasks and send a welcome email
When a new hire is confirmed, an onboarding epic with tasks appears in Jira and the new hire gets a welcome email from you, with their manager copied.
See how it worksKeep exploring
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.