Permissions
Permissions Categories
ScriptRunner for Bitbucket classifies users into the following four categories:
Global Administrators
Global Administrators can access ALL ScriptRunner for Bitbucket features and modify them as required. They can allow Project and Repository Administrators to configure some of ScriptRunner's features as mentioned in Admin-Only Project and Repository Script Access.
Refer to Atlassian's documentation to read more on Global Permissions for Global Administrators (Users with System Admin or Admin permission).
Project Administrators
Refer to Atlassian's documentation to read more on Global Permissions for Project Administrators (Users with Project Creator permission) or Using Project Permissions (Users with Admin permission).
Repository Administrators
Refer to Atlassian's documentation to read more on Using Repository Permissions for Repository Administrators (Users with Repository Admin permission).
Scripts configured by Project and Repository Administrators are run in a sandboxed environment. You can read more information in Repository and Project Scripts for Administrators.
Users
Users (normal Bitbucket users without any of the above roles).
Feature Permissions
The table below lists the main ScriptRunner for Bitbucket features and details the permissions required to use each feature:
| Feature | Specifics | Global Admin Permission | Project Admin Permission | Repository Admin Permission |
|---|---|---|---|---|
| Browse | ||||
| Script Editor | ||||
| Resources | ||||
| Fragments | ||||
| REST Endpoints | ||||
| Jobs | ||||
| Console | ||||
| Built-in Scripts | ||||
| Built-in Scripts | Clone repository configuration | |||
| Built-in Scripts | Repository size report | |||
| Pre Hooks | ||||
| Pre Hooks | Branch and tag naming standards enforcement | |||
| Pre Hooks | Restrict file size | |||
| Pre Hooks | Protect git refs | |||
| Pre Hooks | Reject force push | |||
| Pre Hooks | Reject merge commits | |||
| Pre Hooks | Require commits to be associated with a valid Jira issue | |||
| Pre Hooks | Enforce trusted commit authors | |||
| Post Hooks | ||||
| Post Hooks | Send custom email following code push | |||
| Post Hooks | Respond to pushes with a message | |||
| Post Hooks | Respond to pushes if pull request is outdated or conflicted | |||
| Merge Checks | ||||
| Merge Checks | Prevent merge of pull requests behind target branch | |||
| Merge Checks | Conditional merge check | |||
| Merge Checks | Require that a pull request is associated with a valid Jira issue | |||
| Merge Checks | Require a minimum number of approvers | |||
| Listeners | ||||
| Listeners | Auto-add reviewers to pull requests | |||
| Listeners | Check delete branch checkbox | |||
| Listeners | Auto-merge pull requests on approval | |||
| Listeners | Block out-of-date pull requests | |||
| Listeners | Add tasks to new pull requests | |||
| Listeners | Dynamically add reviewers to pull requests | |||
| Listeners | Withdraw approvals when a pull request changes | |||
| Listeners | Send custom email on event |
For more information on each type of permission, please visit Atlassian's Controlling Access to Code documentation.