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.
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.
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.
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.
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.
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.
Everything teams used to script on the legacy Connect platform - rebuilt for Forge.
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.
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.
Cron-style schedules for daily cleanups, weekly reports, SLA sweeps, and periodic data syncs - one trigger per script, no external scheduler.
React to 30+ Jira events in real time: issues, comments, worklogs, attachments, sprints, versions, components, and projects.
Show, hide, set, require, and rename fields on create and transition forms - including JSM service desk request forms.
Extend Jira's query language: issue in jbExec("myFunction", arg) - return any set of matching issues from a script.
A complete scripting platform built from day one on Atlassian Forge - not a Connect app retrofitted to look modern.
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.
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.
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.
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.
A predictable four-step move - your scripts, your workflows, your data, intact.
Catalog every script, workflow function, scheduled job, listener, and scripted field your team currently runs on the legacy Connect platform.
Install JiBrok Studio from the Atlassian Marketplace. No external accounts, no API keys, no infrastructure to provision.
Rewrite scripts in JS, Python, or Groovy in the Script Console. Use sandbox mode and "Run as user" to validate behavior before going live.
Attach scripts to workflow steps, custom fields, schedules, events, JSM forms, and Jira Automation rules - then retire the legacy Connect app.
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. |
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.
Go deeper on the six most common Forge-native scripting workloads in Jira Cloud.
The app is built on Atlassian Forge - Atlassian's serverless cloud platform - and runs entirely inside Atlassian's infrastructure. Code execution, data storage, and logging all live in Atlassian's cloud. There is no vendor-hosted backend in the data path, no third-party analytics, and no third-party log aggregation inside the app. Read the full architecture overview on the Forge page.
Atlassian ends support for the Connect platform on 31 January 2027, so scripting tools built on it have to be migrated before then. JiBrok Studio is Forge-native from day one, so adopting it removes the Connect dependency entirely - your scripting layer keeps receiving fixes, features, and Atlassian security review after the deadline.
JavaScript, Python, and Groovy - per script. All three languages share a unified API for issues, projects, users, fields, queues, tables, and storage. See the Scripting API reference.
By design, scripts cannot make arbitrary outbound HTTP requests. Data interactions happen through the Jira REST API of the current site and through built-in Forge storage. This keeps data inside Atlassian's cloud and removes a whole class of egress risks. The webhook trigger handles inbound HTTP requests securely.
JiBrok maintains SOC 2 Type II certification for its organizational controls; evidence may be shared under NDA where appropriate. Forge per-installation isolation, scoped storage, and Atlassian's app review process are platform-enforced. Sub-processor lists and DPAs are available in the Trust Center.
Install JiBrok Studio from the Atlassian Marketplace and follow the Getting Started guide. For an end-to-end view of the platform's capabilities, see the JiBrok Studio overview.
JiBrok Studio gives you a complete Forge-native scripting platform - and a clear migration path from any Connect-based scripting solution.