Permissions
Groups with the Jira administrators or Jira System administrators global permission can use and configure ANY ScriptRunner feature.
Groups with the Jira administrators global permission can create or edit any ScriptRunner feature unless the Enable System Admin Only Script Edit Permissions setting has been enabled. When enabled, this setting gives script editing permission to groups with the Jira System administrators global permission only . You can further configure this setting to allow specific groups with the Jira administrator global permission to edit scripts.
Other users
The ability to use configured Scriptrunner features depends if a user has access to the related content in Jira. For example, if Jira's permissions let a user view/access the content within a given area of Jira, any related ScriptRunner features that execute in that context will run. Check out the Atlassian documentation for information on Jira permissions.
The following table lists the main ScriptRunner features and details how Jira permissions impact access to the configuration or use of each feature.
| Feature | Permissions |
|---|---|
| Built-in Scripts | Groups with the Jira System administrators or Jira administrators global permission can use and configure these features. Other users do not have access to use and configure these features. |
| Jobs | |
| Listeners | Groups with the Jira System administrators or Jira administrators global permission can use and configure these features. Other users do not have access to configure these features but can use them providing they have the Jira permissions to perform the Jira action that triggers them. |
| Resources | |
| Mail Handler | |
| Script Editor | Groups with the Jira System administrators or Jira administrators global permission can use these features. Other users do not have access to these features. |
| Script Console | |
| Workflow Conditions, Validators & Functions | Groups with the Jira System administrators or Jira administrators global permission can use and configure this feature. Other users do not have access to configure these features. If a user has permission to view and transition an issue then configured workflow conditions, validators, and post functions will run. |
| Rest Endpoints | Groups with the Jira System administrators or Jira administrators global permission can use and configure this feature. Other users do not have access to configure this feature. The admin configuring the rest endpoint controls who can make a rest call to that endpoint. Admins can define the allowed groups within the script. See the REST Endpoints documentation for more information. |
| Script Fields | Groups with the Jira System administrators or Jira administrators global permission can use and configure this feature. Other users do not have access to configure this feature. If the field has the appropriate Jira context and screen configurations and the user has permission to view an issue, then script fields configured to that issue will display. |
| Behaviours | Groups with the Jira System administrators or Jira administrators global permission can use and configure this feature. Other users do not have access to configure this feature. Behaviours typically trigger when an issue is created, edited, or transitioned. If a user has permission to create, edit, and transition issues, then behaviours mapped to that issue will run. |
| Script Fragments | Groups with the Jira System administrators or Jira administrators global permission can use and configure this feature. Other users do not have access to configure this feature. A script fragment renders new UI elements, hides existing ones, or adds additional js/css to the page. If a user has permission to view the page where the fragment is located, the script fragment runs and either adds or removes the configured elements. |
| JQL Functions | Only groups with the Jira System administrators or Jira administrators global permission can create custom JQL functions. Other users can use a number of out-of-the-box JQL functions if they have permission to search for issues (for example if a user has permission to browse projects in Jira they can search for issues). Check out the Included JQL Functions page to find out more about ScriptRunner JQL functions. If a user does not have permission to see a given project/issue, then the result of a JQL search does not include the restricted projects/issues. |