Last updated Jan 10, 2022

Jira Service Management operations scopes for OAuth 2.0 (3LO) and Forge apps

Scopes enable an app to request a level of access to an Atlassian product.

Jira Service Management operations permissions also control access to data and aren't overridden by scopes. For example, if a user does not have Jira Administrator Global permission or Team Admin rights then the Create Schedule operation won’t be able to create schedule even if the app has the write:ops-config:jira-service-management scope.

Setting your app's scopes

Forge apps

The easiest way to set your app's scopes is to:

Update to the latest forge-cli packages.
Run forge-lint --fix to add the scopes to the manifest.

This process does not remove any redundant scopes from the manifest file, and these scopes need to be removed manually.

If you want to set the scopes manually, you need to:

Review your app to determine all of the operations used.
Consult the Jira Service Management operations REST API documentation to determine the scope needed for each operation and create a list of scopes.
Add the scopes required to the app's manifest file while remembering to remove any deprecated scopes.

OAuth 2.0 apps

For OAuth 2.0 apps, you need to:

Review your app to determine all of the operations used.
Consult the Jira Service Management operations REST API documentation to determine the scope needed for each operation and create a list of scopes.
Update the scopes required in the developer console.

Scopes

These scopes are for apps using OAuth 2.0 authorization code grants (3LO) for authorization and Forge apps. The title and description are displayed to the user on the consent screen during the authorization flow.

Scope name	Summary	Description
`read:ops-config:jira-service-management`	Read Jira Service Management operations configuration	Read configuration of operations including contacts, custom user roles, escalations, forwarding rules, heartbeats, integrations, maintenances, notification rules, routing rules, schedules, on-calls, and syncs.
`write:ops-config:jira-service-management`	Create and manage Jira Service Management operations configuration	Create and edit configuration of operations including contacts, custom user roles, escalations, forwarding rules, heartbeats, integrations, maintenances, notification rules, routing rules, schedules, on-calls, and syncs.
`delete:ops-config:jira-service-management`	Delete Jira Service Management operations configuration	Delete configuration of operations including contacts, custom user roles, escalations, forwarding rules, heartbeats, integrations, maintenance, notification rules, routing rules, schedules, on-calls, syncs.
`read:ops-alert:jira-service-management`	Read Jira Service Management operations alert data	Read operations alert data, including request status, alert logs, and listing and searching for alerts.
`write:ops-alert:jira-service-management`	Create and manage Jira Service Management operations alerts	Create and edit alerts, including status, description, priority, attachments, tags, and notes.
`delete:ops-alert:jira-service-management`	Delete Jira Service Management operations alerts	Delete the alerts.