React in real time to 30+ Jira events - issues created, updated, assigned, commented; worklogs, attachments, issue links, versions, components, projects, sprints, boards. Forge-native, with full event payloads and a built-in self-event filter that prevents loops.
Some automations are time-based - they belong on a schedule. Others have to fire the moment something happens: an issue is created, a comment is added, a sprint is closed. Event listeners are the right primitive for those - they hand your script the event payload at the exact moment Jira fires the event.
Teams have built event-driven scripts on Jira for a decade. Many of those listeners currently live in legacy Connect-based scripting tools. With Atlassian Connect reaching full end of support on 31 January 2027, those listeners need a Forge-native home - one that runs inside Atlassian's cloud and benefits from the platform's tenant isolation.
JiBrok Studio supports more than 30 Jira event types out of the box, each delivering a structured event variable to your script - so you can react to exactly what happened, on the issue or object that triggered it.
When a user is @-mentioned in a comment, check whether they belong to a specific approvals group and, if so, set the issue's approval status field.
Event: comment_mentioned
On issue creation, scan the description for issue keys and create "relates to" links automatically. No more orphaned tickets in the backlog.
Event: issue_created
When a sprint closes, post a structured summary - completed vs carried-over points, top contributors, defects opened - on a tracking issue.
Event: sprint_closed
Select multiple events on one trigger to share the same handler.
The built-in self-event filter prevents your script from re-triggering itself when it updates the issue that fired the event - the single most common foot-gun in event-driven scripting. It is always on; there is nothing to configure.
For heavy or fan-out work that should not block the originating event, push tasks to an async event trigger backed by a priority message queue.
On issue creation, auto-link any issue keys mentioned in the description.
// Event trigger: issue_created
const created = event.issue;
// Description is stored as ADF - Adf.toText() flattens it to plain text
const desc = Adf.toText(created.fields.description) || '';
const keys = (desc.match(/\b[A-Z][A-Z0-9_]+-\d+\b/g) || [])
.filter(k => k !== created.key);
for (const key of new Set(keys)) {
try {
Issues.link(created.key, 'Relates', key);
log(`Linked ${created.key} -> ${key}`);
} catch (e) {
log(`Could not link to ${key}: ${e.message}`);
}
}Save the script and add an Event trigger for issue_created. Every new issue is processed within seconds of creation - all inside Atlassian's cloud, with the self-event filter already keeping the script from re-triggering itself.
JiBrok Studio's event listeners run on Atlassian Forge - your event data and your scripts stay inside Atlassian.