Skip to main content

Failures on forms

When a UI modification fails on a form, Script Master counts the failure and shows it in the list and the editor. This page explains what each failure means and what to do.

Applies to: Script Master for Jira Β· Cloud

The form keeps working when a UI modification fails: Jira shows it as if that UI modification didn't exist.

Where failures show​

  • In the list, the Failures column shows the count, for example 3 failures. Hover over it to see the last error.
  • Select Failing above the list to see only the UI modifications that failed.
  • The Last 7 days column shows failures per day. Days are in UTC.
  • In the editor, a message at the top gives the number of failures since its rules, script or scope last changed, and the last error.

The editor's warning: failed 3 times on forms since its rules, script or scope last changed, with the last failure

The count is a minimum: Script Master records failures for one UI modification at most once every 5 minutes. Forms that load without errors aren't counted. The count starts again from zero when you save a change to the rules, script or scope. Renaming it or turning it on or off keeps the count.

What a failure means​

The message starts withWhat it meansWhat to do
The script failedThe script threw an error. Script errors include the line, for example The script failed: Line 4: Cannot read properties of undefined (reading 'id').Fix the script at that line.
Another app changes the same field, and Jira kept only one changeAnother app's UI modification changes the same field.Change a different field, or limit where one of them runs.
Jira rejected a value or settingJira refused a value or setting for a field, for example a value of the wrong type.Check the value in the rule or script.
The script changes a field it does not declare in "scriptFieldIds"The script changes a field Jira doesn't know it uses.Declare the field. See Fields a script can change.