Skip to main content

πŸ“‚ Script Master

Script Master logoScript Master lets Jira and Confluence admins add their own scripts to the site: panels and actions on work items and pages, dashboard gadgets, macros, calculated fields, workflow rules, form changes, scheduled jobs and URLs other systems can call. You write JavaScript, or build rules without code, on one admin page, and switch each item on when it's ready.

Get started: install the app and run your first script in about 10 minutes.

The Script Master admin page in Jira on the Overview tab, with what needs attention, recent changes and the items on the site

Why teams use it​

  • One app for many small changes. A panel on work items, a dashboard gadget, a Confluence macro, a required field on a transition and a nightly clean-up all live in one place, so you don't install a separate app for each.
  • No build, no deploy. You write and test scripts in the Script Master admin page and turn them on there. There's no project to build and no app to deploy, except the Companion App you set up once for server scripts.
  • Start from working code. Templates and snippets cover common tasks, such as listing a work item's contributors or requiring details for urgent work. A live preview runs your code with real data before anyone else sees it.
  • Rules without code. Build validators, conditions and UI modifications from plain checks, such as Due date is set. Script Master writes the code for you.
  • Safe to change. Every save is a version you can compare and restore. Run history, failure banners and the Overview tab show what ran, what failed and what changed.
  • Clear about who scripts run as. Scripts in the browser run as the person using them, with their permissions. Server scripts run as the app, in a Companion App you deploy under your own developer account.

Who it's for​

  • Jira admins add fields, workflow rules, form changes and work item panels that Jira doesn't offer out of the box.
  • Confluence admins build macros and page actions for their teams, and make bulk changes to spaces and labels.
  • Service desk admins add pages to service queues and adjust request forms in the service portal.
  • Atlassian consultants and in-house developers connect Jira and Confluence to other systems through web triggers and scheduled jobs, and keep every script on the site in one admin page.

What you get in each product​

FeatureJiraConfluence
Script Console: run one-off scripts and bulk changes as yourselfYesYes
Fragments: your own HTML and JavaScript in the product's UIWork item panel, work item action, space page, space settings page, queue pagePage action, page byline item, space page, space settings page
Gadgets on dashboardsYesNot available
Macros people insert into pagesNot availableYes
UI Modifications: show, hide, require, lock, rename or pre-fill fields, and limit select options, while people fill in a formCreate dialog, transition screens, work item view, service portalNot available
Scripted custom fieldsNumber, text, user, date and date-time fieldsNot available
Workflow post functions, validators and conditionsYes, validators and conditions also without codeNot available
Web Triggers: a URL that runs your scriptYesYes
Scheduled JobsYesYes
Script Master Tools: bulk changes without a script, for the groups you choose2 tools7 tools
Version history, run history and the Overview tabYesYes
Marketplace appScript Master for JiraScript Master for Confluence

The two apps are separate Marketplace listings with separate licenses. Install the one for each product you use.

Web triggers, scheduled jobs, scripted fields and post functions run on a server: a small Companion App that you deploy and connect once. Everything else works as soon as the app is installed.

Documentation​

SectionWhat you'll find
Get startedInstall the app, open it in Jira or Confluence, and run a first script
Use casesContributors on work items, details for urgent work, a nightly job, alerts into Jira and a calculated field
Using Script MasterThe admin page: tabs, Overview, version history, run history, failures, import and export, and Settings
Script ConsoleRun scripts in the browser, with snippets and examples
Fragments, Gadgets and MacrosAdd your own UI to work items, pages, spaces and dashboards
UI ModificationsChange Jira forms while people fill them in, with rules or a script
Custom fields and Workflow extensionsScripted fields, post functions, validators and conditions in Jira
Web Triggers, Scheduled Jobs and ListenersRun scripts when another system calls, on a schedule, or from Jira Automation
Script Master ToolsBulk changes to work items, pages, labels and spaces, with no script to write
Code editorThe editor, the external editor, Build script with AI and the AI prompt pages
Forge bridge API for browser scripts and Forge API for server-side scriptsThe APIs your scripts can call
AdministrationInstall and update, permissions, licensing and the Companion App
Set up the Companion App and Data security and privacyHow server scripts run, what the app stores, and where data goes
Move a script to your own Forge appTurn a fragment, gadget or other script into a standalone Forge app
ReferenceLimits, known limitations, and differences between Jira and Confluence
Troubleshooting and FAQFixes for common problems, and short answers

What's new​

  • Q3 2026: Script Master Tools for bulk changes, who created and changed each item, and Build script with AI. Details
  • Q1 2026: Server scripts run only in your Companion App. Details
  • All changes

Get help​