Release notes

Every version that reached the Marketplace, newest first, for both listings. They share one history and carry their own numbers: the first release is 2.4.0 for Jira and 2.0.0 for Confluence.

2.9.0, 04.11.2026

A maintenance release: internal clean-up and documentation. Nothing changes in how the app behaves, and no permission changed. Code Studio for Confluence is 2.4.0 in its listing.

2.8.0, 03.11.2026

2.8.0 for Jira and 2.3.0 for Confluence. Fixes from our penetration test of 03.11.2026.

• A developer’s run imports only from spaces they can see. A console, Rovo or field preview run could import a script from a restricted space and return its code. Administrators and trigger runs still see every script.
• A field that fails to create leaves nothing behind in Jira. The half-made field goes to Jira’s trash.
• The limit of 10,000 waiting calls holds after a script’s memory grows, and ends with the usual error.
• Check script warns when a script calls a deprecated Atlassian REST path.
• Add trigger opens the trigger form for the script again.

2.6.0, 01.11.2026

2.6.0 for Jira and 2.1.0 for Confluence.

• store belongs to the script’s space. A script in another space can no longer read or overwrite its values. store.shared holds the site’s values, for runs an administrator or a trigger starts. Values stored before this version stay under their old keys and are not read.
• Any run stops within 7 seconds, a tight loop with no await included. A run whose function passes 900 MB of memory ends with a memory error, and the next run starts as usual.
• A connection’s credential stays on its own origin. A redirect to another host is followed without it, and a run’s Web requests hide it.
• A connection to an Atlassian host refuses a header named Authorization, Proxy-Authorization or Cookie, as it refuses basic sign-in.
• A picked field reads its choices again about 30 seconds after a context is saved in Jira’s field screen. An options() that returns nothing keeps the choices the field had.
• A schedule switched off or changed cancels the runs it queued. Stopping a production run takes the same right on the space as starting one.
• Optimize a script in Script with Rovo, and conversions between TypeScript and JavaScript both ways. A test event can be built from a real work item, page or space, and Web requests lists reads as well as writes.

What the Application collects and where it goes stay the same.

2.4.0, 21.10.2026

The first Marketplace version, 2.4.0 for Jira and 2.0.0 for Confluence, in two listings with the same features: Oktul Code Studio for Jira and Oktul Code Studio for Confluence. Install the one for your site’s main product.

A console in the Apps menu to write JavaScript, TypeScript and AssemblyScript scripts in spaces, with completion, revisions, publishing and live co-editing. A space can be kept in step with a GitHub, Bitbucket Cloud or GitLab repository, or any other Git host over HTTPS. A sandbox that reads the site and lists every write instead of sending it. Scripts run from listeners on Jira and Confluence events, cron schedules, a Jira automation action and API triggers; a scheduled run is queued ahead of its minute and starts on it, continues past Forge’s time limit up to three times, and can be cancelled while it waits or stopped at any moment. Connections that keep credentials from scripts, script variables, and hosts approved in Atlassian’s dialog. Scripted Jira fields, picked or computed, with values refreshed on the events they depend on or on a timer, and dynamic forms on the create, transition and portal screens. Five Rovo agents: a translator for ScriptRunner Groovy, an author, a debugger, an optimizer and an editor, and the same tools for Claude and other MCP assistants once an administrator turns them on. Export and import of the whole configuration. English.

A change to what data is collected, where it goes or who can see it is stated here and in the privacy notice.