Known limitations
What Script Master doesn't do today, and what to do instead.
Running scriptsβ
| Limitation | What to do instead |
|---|---|
| Server-side scripts need the Companion App. Web triggers, scheduled jobs, scripted fields and post functions don't run without it. | Set up the Companion App once per site. |
| No script listeners. Script Master doesn't run scripts on Jira events such as a work item being created or updated. | Use Jira Automation, or call a web trigger from a Jira Automation flow. See Listeners. |
| Scheduled jobs run at most once an hour, and can start up to an hour after their time. A schedule that fires more often still runs once an hour. | Use a web trigger called by an outside scheduler when timing matters. |
| Web trigger URLs have no sign-in. Anyone with the URL can call it. | Check a secret or the caller inside the script. See Web Triggers. |
| Validators and conditions aren't counted when they pass. Jira only reports expressions it couldn't evaluate, so Last 7 days shows those failures and nothing else. | Use Test on a work item in the rule editor to check a rule before you save it. |
| Browser scripts record failures, not views. Fragments, gadgets, macros and UI modifications show failures in their history, but not how often they ran. | - |
Previews and historyβ
| Limitation | What to do instead |
|---|---|
| "View as" in a live preview only changes the context. The preview's requests still use your own permissions, because Forge can't act as another person. | Check what someone else sees by signing in as a test user. |
| Live previews never pass a Macro Body. A real page would let a template act on real content. | Make your macro handle a missing context.extension.config.macroBody. |
| The field preview's "Now" value is what Jira stored, which can be older than what the field would calculate today. | Compare with the new value in the same row. |
| Workflow rule versions only come from Script Master's editor. Changes made elsewhere aren't versions. | Edit rules in Script Master's editor. |
| Space admins of team-managed spaces can't open version history or Recent runs for workflow rules. Both need a Jira admin. | Ask a Jira admin. |
Working on the admin pageβ
| Limitation | What to do instead |
|---|---|
| Leaving through Jira's or Confluence's own navigation doesn't ask about unsaved changes. A Forge app can't stop that link. | Your changes stay in this browser for 7 days. Open the list again and select Restore on the message that starts Unsaved changes to. |
| The first Confluence Overview load after an update can take up to 20 seconds. | Wait for it. Later loads are faster. |
| Script Console code is kept only in your browser. | Save scripts you want to keep somewhere else, for example as a scheduled job or in your own repository. |
Productsβ
| Limitation | What to do instead |
|---|---|
| Gadgets, UI Modifications, Custom Fields and Workflows are Jira only. Macros are Confluence only. | See Jira and Confluence differences. |
| Cloud only. Script Master isn't available for Jira or Confluence Data Center. | - |
Relatedβ
- Limits: the numbers.
- Troubleshooting: fixes for specific problems.
- FAQ: short answers to common questions.