Skip to main content

FAQ

General Questions​

Who can access Script Master for Jira or Confluence?​

Script Master is accessible to application administrators who have the necessary permissions to install and configure apps within their instance.

Is Script Master for Jira compatible with all Jira products?​

Yes, Script Master for Jira is compatible with all Jira products, including Jira Work Management, Jira Software, and Jira Service Management.

Script Console​

What is the Script Console?​

The Script Console is a hub for automations within Script Master. It provides tools such as REST API Exploration, Bulk Updates, and Automate Admin Tasks to execute scripts and automate routine administrative duties.

Can I execute scripts in the Script Console as any user?​

No, scripts executed in the Script Console run within the context of the current user and follow their permissions. Users can only read or modify content that they have access to.

Fragments​

What are Fragments?​

Fragments are UI components that extend the interface of Jira or Confluence to display Custom Actions or other Custom UI elements. They allow users to add new functionalities or enhance data visualizations within their application.

In which Jira views do Fragments work?​

Fragments work in the new issue view of Jira, but they are not compatible with the old issue view.

Web Triggers​

What are Web Triggers?​

Web Triggers are JavaScript functions running on the Forge back end that respond to HTTP requests. They provide a powerful way to integrate external systems with Jira or Confluence and automate workflows without requiring user authentication.

Can Web Triggers interact with Jira or Confluence?​

Yes, Web Triggers can interact with Jira or Confluence on behalf of the app using the useApp() method. This enables them to perform various actions, such as creating or updating content, querying data, or triggering workflows.

Security​

Where is my data stored? Does Script Master use any external databases?​

Script Master is a 100% native Atlassian Forge app. All data is stored exclusively within the Atlassian Forge environment on your own cloud instance. We do not operate any external databases, and no data is ever processed or transmitted outside of Atlassian's infrastructure.

For a full breakdown suitable for vendor security reviews, see the Data Storage & Security page.

Are Web Triggers secure by default?​

No, Web Triggers are not secured out of the box. Administrators need to implement authentication functionality to ensure that only authorized users or systems can trigger the Web Triggers.

How can I secure Web Triggers?​

To secure Web Triggers, administrators can implement authentication mechanisms such as token-based authentication. An example of this can be found in the Snippets Library, which utilizes request headers to check for a proper token provided in them.

By implementing authentication, administrators can ensure that only trusted sources can access and trigger the Web Triggers, enhancing the overall security of their Jira or Confluence instance.

Support and Documentation​

How can I get support for Script Master for Jira?​

For support or assistance with Script Master, you can contact our customer support team or visit our community forums to connect with other users and developers.

Scheduled Jobs​

Why didn't my scheduled job run at the exact time I configured?​

Scheduled Jobs use the Forge Async Events API, which does not guarantee execution at an exact time. Delays of up to 60 minutes are possible. Design your scripts to tolerate timing variability and avoid depending on strict execution schedules.

My scheduled job appears to have run but produced no output or log. What happened?​

Scheduled Jobs have a maximum execution time of 55 seconds. If a job exceeds this limit, it will fail silently — no error appears in the job history. Break long-running tasks into smaller units to stay within the time limit. See Scheduled Jobs limitations for more details.

How do I debug a scheduled job?​

Add console.log() statements to your job script to capture key values at each step. Logs are visible in the Script Master interface. For complex jobs, test the core logic first in the Script Console before deploying it as a scheduled job.

Custom Fields​

My scripted custom field shows an empty value on existing issues. Why?​

Scripted custom fields only calculate their value when a user opens the issue in Issue View. Issues that have never been opened after the field was added will show no value. Use the Reindex feature to populate values for all existing issues at once.

The custom field value is not updating when an issue is changed via automation or REST API. Why?​

Custom field values recalculate only when a user opens the issue view, not when the issue is updated by automation or background processes. This is a known Forge platform limitation. For more details, see Performance and Limitations.

What return types are supported for scripted custom fields?​

The return value must match the field type:

  • Number field: return a JavaScript number
  • String field: return a JavaScript string
  • Datetime field: return a string in ISO 8601 format (e.g. "2025-06-01T09:00:00.000Z")
  • User field: return an object with an accountId property (e.g. { accountId: "abc123" })