Which language are scripts written in?

JavaScript. Fragments and gadgets are HTML with JavaScript that runs in the viewer's browser; backend scripts are modern JavaScript with top-level await, run in an isolated sandbox inside the app.

Who can write scripts?

Only Jira admins. Fragments and gadgets then run for everyone who views them, with each viewer's own permissions; bulk tools can be opened to chosen groups.

Do scripts run on external servers?

No. Everything runs on Atlassian Forge, inside your Jira site. Yamuno runs no servers for the app and receives none of your data.

Can a backend script change Jira?

Only if you allow it. Each backend script is read only by default; set its Jira access to Read and write when it needs to create or change data.

Can scripts call other services?

Backend scripts can, with fetch, but only if you allow it under Settings: off, a list of hosts you choose, or any public https host. Private and internal addresses are always refused.

Where do I keep API keys?

Under Settings → Secrets. Values are kept in Forge's encrypted secret storage, can't be read back from the UI, and are masked in logs.

Is there a limit on how much scripts run?

Yes. Each site has daily limits for backend runs and scripted field runs, and a time limit per run. Admins can adjust them within set ranges.

for Jira

Script Toolkit for Jira

Script Jira Cloud in JavaScript: panels, gadgets, triggers, jobs, fields and workflow rules

Write JavaScript to extend Jira Cloud: your own panels on work items and project pages, dashboard gadgets, web triggers for other systems, scheduled jobs, scripted fields and workflow validators. Backend scripts run in an isolated sandbox on Atlassian Forge, read only unless you allow writes.

Launching on the Atlassian Marketplace soonRead the docs

Script Toolkit for Jira running inside Jira

What Script Toolkit for Jira does

Script Console
Run JavaScript against your Jira from the browser, with your own permissions, before saving anything
Fragments
Your own HTML and JavaScript on work items, in a dialog and on project pages; several in one place become tabs
Dashboard gadgets
Build gadgets from scripts and pick one per gadget on any dashboard
Web triggers
A secure URL with its own secret for each trigger, returning whatever your script returns
Scheduled jobs
Cron schedules in UTC for reports, clean-ups, syncs and reminders
Scripted fields
Text, number, user, date and date time fields computed by a script
Workflow validators and post-functions
Block a transition with a message, or act after it
Bulk tools
Seven bulk tools for work items, opened per tool to admins, groups or everyone
Safe by default
Isolated sandbox, read-only Jira access unless allowed, outbound calls by host, encrypted secrets and daily limits

What changes for your team

Add the panel your team keeps asking for to every work item, in HTML and JavaScript, without building a whole app
Connect CI, monitoring and other tools to Jira with a web trigger: a secure URL with its own secret
Run reports, clean-ups and syncs on a cron schedule
Compute custom fields and enforce rules on workflow transitions with a few lines of code
Let team leads run bulk changes safely: each tool is opened per group, and runs with their own permissions
Keep control: backend scripts are read only unless you allow writes, and outbound calls go only to hosts you list