Forge-native scripting for Jira Cloud

Write JavaScript, Python, or Groovy that runs entirely inside Atlassian's cloud. No external servers, no third-party data egress, no legacy Connect lifecycle - just modern scripting that is Forge-native by design and needs no external infrastructure.

Forge Native
JS · Python · Groovy
SOC 2 Type II
Connect EOS Ready

Why Forge-native scripting matters

Atlassian Connect reaches end of support on 31 January 2027. Scripting tools built on the legacy Connect platform have to be replaced before then - and the replacement should not introduce new external systems.

Connect EOS deadline

Atlassian ends support for the Connect platform on 31 January 2027. After that date any Connect-based scripting tool you rely on stops receiving fixes.

No vendor servers

Forge apps run on Atlassian's serverless runtime. Your scripts and data never leave Atlassian's cloud - there is no vendor-hosted backend in the data path.

Tenant isolation

Every installation's data is isolated by the Forge platform: storage is scoped to the installation, and the app has no network egress outside Atlassian.

Automatic updates

Fixes are rolled out by the platform to every installation without administrator action; only a release that adds new permissions waits for administrator approval. No version fragmentation, no maintenance windows.

Top use cases

Everything teams used to script on the legacy Connect platform - rebuilt for Forge.

Workflow automation

Post-functions and validators that run scripts on every transition - with the full issue, transition, and modified-fields context - plus workflow conditions evaluated as Jira Expressions.

Scripted custom fields

Nine computed field types - text, number, date, datetime, rich text, user, user list, group, group list - that recalculate on issue create and update, including ADF content.

Scheduled jobs

Cron-style schedules for daily cleanups, weekly reports, SLA sweeps, and periodic data syncs - one trigger per script, no external scheduler.

Event listeners

React to 30+ Jira events in real time: issues, comments, worklogs, attachments, sprints, versions, components, and projects.

Dynamic forms (JSM & Jira)

Show, hide, set, require, and rename fields on create and transition forms - including JSM service desk request forms.

Custom JQL functions

Extend Jira's query language: issue in jbExec("myFunction", arg) - return any set of matching issues from a script.

How JiBrok Studio delivers Forge-native scripting

A complete scripting platform built from day one on Atlassian Forge - not a Connect app retrofitted to look modern.

One platform, three languages

Choose JavaScript, Python, or Groovy per script. A unified API gives every language the same access to issues, projects, users, fields, queues, tables, and storage - so migrating snippets between languages is a matter of syntax, not architecture.

Scripting API reference →

Interactive Script Console

Write, test, and iterate inside Jira. Syntax highlighting, autocomplete, structured logs, sandbox mode for safe testing, and a "Run as user" option for permission checks - the developer-experience parity teams expect from a serious scripting tool.

Script Console docs →

A shared Script Library

Save scripts to a team library with folders, labels, full version history, diff view, and import/export. Track exactly where every script is used across workflows, fields, and triggers.

Script Library docs →

Every trigger you need

Scheduled, event, webhook, async event, workflow post-function, workflow validator, workflow condition, JQL function, UI modification, scripted field, and Jira Automation action - all in one app.

Triggers overview →

Migration path from legacy Connect scripting

A predictable four-step move - your scripts, your workflows, your data, intact.

1

Inventory

Catalog every script, workflow function, scheduled job, listener, and scripted field your team currently runs on the legacy Connect platform.

2

Install Studio

Install JiBrok Studio from the Atlassian Marketplace. No external accounts, no API keys, no infrastructure to provision.

3

Port & test

Rewrite scripts in JS, Python, or Groovy in the Script Console. Use sandbox mode and "Run as user" to validate behavior before going live.

4

Wire triggers

Attach scripts to workflow steps, custom fields, schedules, events, JSM forms, and Jira Automation rules - then retire the legacy Connect app.

Trust & security signals

Security guarantees enforced by the Forge platform, not just promised by the vendor.

Guarantee How it is enforced
SOC 2 Type II JiBrok maintains SOC 2 Type II certification for its organizational controls; evidence may be shared under NDA where appropriate. See the Trust Center.
Tenant isolation Every installation's data is isolated by the Forge platform: storage is scoped to the installation, and the app has no network egress outside Atlassian.
No external egress Scripts cannot send data to arbitrary external URLs. All execution stays inside Atlassian's cloud.
Scoped storage All data stored in Forge SQL and KV is per-installation. One tenant cannot access another's data.
Atlassian app review The app and its declared permissions are reviewed by Atlassian at listing and whenever the permission set changes; the platform blocks anything the manifest does not declare.
Audit logs Script executions are recorded with the actor, source, duration, and output, and are available to admins in the Script Runs audit.

In simple terms

When you install JiBrok Studio, it runs as a function inside Atlassian's cloud - the same way built-in Jira features do. There is no JiBrok server receiving your data. There is no external database storing your scripts. There is no third-party service watching what you do.

Everything in the data path stays inside Atlassian.

Learn about our Forge architecture

Specific scripting scenarios

Go deeper on the six most common Forge-native scripting workloads in Jira Cloud.

Jira automation scripts

Automate Jira with scripts: trigger code from Automation rules, workflow transitions, events, and schedules.

Scripted custom fields

Computed custom fields - nine types, from text and number to user and group lists - that recalculate on issue create and update.

Workflow validator scripts

Block invalid transitions, enforce policy, and return custom error messages - before the transition is applied.

Scheduled jobs

Run scripts on a cron schedule - daily cleanups, weekly reports, SLA sweeps, periodic syncs.

Event listeners

React to 30+ Jira events - issues, comments, worklogs, sprints, versions, components - in real time.

JSM dynamic forms

Show, hide, set, and require fields on JSM request forms and Jira create / transition screens.

Frequently asked questions

Move your scripting layer to Forge before the Connect EOS

JiBrok Studio gives you a complete Forge-native scripting platform - and a clear migration path from any Connect-based scripting solution.

JiBrok Studio for Jira Cloud JiBrok Studio for Jira Cloud
JiBrok Message Field for Jira Cloud Message Field for Jira Cloud
JiBrok time in status Time in status for Jira Cloud
JiBrok time in status Time in Status (Forge) for Jira Cloud
Calculated Fields (Forge) Calculated Fields (Forge) for Jira Cloud
JiBrok Calculated fields Calculated fields (JBCF) for Jira Cloud
JiBrok Timer Timer field | SLA for Jira Cloud
JiBrok Stopwatch Stopwatch for Jira Cloud
JiBrok Time between dates Time between dates for Jira Cloud
JiBrok Fields panel for Jira Service Management (JSM) Fields panel for Jira Service Management (JSM)
JiBrok Display Linked Issues Display Linked Issues
JiBrok Display Linked Issues Display Linked Issues
JiBrok message field Message field
JiBrok time in status Time in status | SLA | Timer | Stopwatch
JiBrok Switch to User + Delegating SU (Jira) Switch to User + Delegating SU (Jira)
Group Delegate & Creation Management (Jira)
JiBrok Calculated fields Calculated fields (JBCF)
JiBrok Timer Field Timer Field (Forge) for Jira Cloud
JiBrok Stopwatch Field Stopwatch Field (Forge) for Jira Cloud
JiBrok Time Between Dates Time Between Dates (Forge) for Jira Cloud
JiBrok Display Linked Issues Display Linked Issues (Forge) for Jira Cloud
JiBrok Customer Portal Fields Panel Customer Portal Fields Panel (Forge) for JSM
rss
rss
rss