Tools

Compatibility

This module is available for both the Jira and Confluence versions of the app. The tool catalogue differs per product.

Overview

Tools are ready-to-use, no-code utilities for bulk operations and routine administrative tasks. Unlike the rest of Script Master, tools require no scripting at all — you fill in a short form and run the operation.

Tools live on their own Script Master Tools page, separate from the admin area. This is the one part of Script Master that administrators can open up to non-administrators: each tool has its own access rule, so you can hand a specific bulk operation to a group of project leads or space admins without granting them access to the Script Console or any other module.

Accessing the Tools page

The Tools page is a global page provided by the app and is not part of the Script Master admin area.

In Jira

Open the Apps menu in the top navigation and select Script Master Tools.

In Confluence

Open the Apps menu in the top navigation and select Script Master Tools.

The page lists every tool the current user is allowed to use. Selecting a tile opens the tool's form. If no tools have been made available, the page shows an empty state instead.

The question-mark menu in the top-right corner of the page links to this documentation and to support.

Configuring who can use each tool

Access is configured by an application administrator:

1. Open Script Master from the administrator menu.
2. Go to the Tools tab.
3. Choose an access level for each tool in the list.
4. Click Save.

Each tool has its own rule — there is no single setting for the whole module:

Access level	Who sees the tool
All users	Everyone who can open the Tools page
Restricted to groups	Only members of the groups you select
Disabled	Nobody; the tool is hidden from the Tools page

Default access

A tool that has never been configured behaves as All users. This means new tools shipped in an app update appear on the Tools page immediately. If your organization prefers tools to be opt-in, review the Tools tab after each app update.

How access is enforced

Filtering happens on the Forge backend: the list of tools is computed server-side from the calling user's group membership, and the group configuration itself is never sent to end users. A tool that is not permitted is not merely hidden in the UI.

Tools run with the permissions of the user who runs them, not with administrator permissions. A user who lacks permission on a target issue, page, or space will see the operation fail for those items even when the tool itself is available to them.

Available tools

Jira

Tool	What it does
Bulk Set Resolution	Sets the resolution field on many issues at once, selected by JQL.
Copy Custom Field Values	Copies values from one custom field to another across issues selected by JQL.

Confluence

Tool	What it does
Clone Space	Creates a full copy of a space, including its pages and structure.
Replace Label	Replaces a label across pages, blog posts, and attachments in the spaces you select.
Add Label to Parent Pages	Adds a label to a page and all of its ancestors, up to the space root.
Add Label to Child Pages	Adds a label to a page and all of its descendants, at any depth.
Delete Attachments	Bulk-removes attachments across a space to reclaim storage. Listed in the catalogue; the form is not implemented yet — selecting it shows the description only.

Not finding the operation you need?

The tool catalogue is deliberately small and grows with each release. Anything a tool cannot do can still be scripted — see the Script Console for ad hoc bulk operations and Scheduled Jobs for recurring ones.

Notes and limits

• Tools operate on live data and most of their actions cannot be undone. Test on a small JQL result set or a sample page tree first.
• Tools run from your browser and call the Jira or Confluence REST API directly. Keep the browser tab open until the tool reports completion — closing it stops the operation partway through.
• Bulk tools process matches in pages of 100 and stop at 5,000 matching items per run. Narrow your JQL or split the work if you need to cover more.
• Atlassian rate limits apply. If the API starts throttling, the tool backs off and reports the affected items rather than failing silently.
• Group selection stores group names. If a group is renamed in your identity provider, update the affected tool rules.
• The Tools module stores only its access configuration; see Data Storage & Security.