Permissions are settings within Jira applications that control what users in those applications can see and do. This page describes the different types of permissions and access rights that can be configured in The Scheduler.

These permissions can be set for The Scheduler hosted on:

The Scheduler for Jira Cloud

Note: In v3.2.0, we changed a bit permissions behaviour to match the Data Center / Server behaviour. Now users with ‘Administer project’ permissions, but without ‘Create issue' permission (even without ‘The Scheduler: Use’ permission), can access the Scheduled Issues table and preview all Scheduled Issues, with special warning banner.

In other words: project admins gets more visibility.

Project permissions are managed in two ways:

Jira administrators manage project permissions for company-managed projects through permission schemes.
Project administrators manage project permissions for team-managed projects through custom roles.

The Scheduler transitions from Access Manager into “Jira style” permissions with support for Global and Project custom permissions. What to expect from app with given/lack of permissions?

In Team-managed projects any permission or access in project is controlled on the Access page. Here you can add people to your project and give them a role so they can start collaborating on your team’s work. Your project’s access level sets general permissions for people across your Jira site. You can give specific access or permissions to individual people by creating your own project roles.

Project Settings → Access

Image 1: Team-managed project - Access level

Every company-managed project has a permission scheme. A permission scheme grants users, groups, or roles their permissions in company-managed projects.

This page discusses what are the types of errors to be expected when some global/project permissions is missed or extra added in settings of Company Managed Project.

Type of permissions:

1 1a. App’s global permission: The Scheduler: Access.
2 1b. Browse project permission.
3 1c. App’s project permission: The Scheduler: Use.
4 1d. Create issue permission.

1a. App’s global permission: The Scheduler: Access.

Project and Global Administrators are granted this by default. To change global permission, you must be a site admin or a Jira admin.

Here is an example from Jira Cloud configuration in Company Managed project:

Jira Settings → Global Permissions → The Scheduler: Access

Image 2: Granted Global permission - The Scheduler Access

1b. Browse project permission.

This permission allows people to view the project in the Projects directory and view individual issues in the project also while searching Jira. Without Browse projects permission users can’t access projects, thus cannot access The Scheduler.

User Permission	Atlassian addon permission	Result of lack/grant permissions on screen

User Permission	Atlassian addon permission	Result of lack/grant permissions on screen

Table 1: Browse permission with messages of lack or grant User and Altassian addon permission

1c. App’s project permission: The Scheduler: Use.

Project and Global Administrators are granted this by default - to ensure app can be used and managed. Global permission “The Scheduler: Access” is required. Jira Administrators and Project Administrators have access to all Scheduled Issues in project.

Project Settings → Permissions → The Scheduler: Use

1d. Create issue permission.

This permission allows people to create issues in your project, including subtasks if you’ve enabled subtasks on your site. If in Project settings there will be lack of Create permission, the missing permissions banner should be visible above the Scheduled Issues table.

Here are combinations of missing permissions (User, Addon and Atlassian addon permission) and the result on your project:

User	Addon	Atlassian addon permission	Result of lack/grant permissions on screen

User	Addon	Atlassian addon permission	Result of lack/grant permissions on screen

Table 2: Create issue permission with messages of lack or grant User, Addon and Altassian addon permission

The Scheduler for Jira Data Center

In this section you will learn about the different permissions in Jira Server (and Data Center) and this page shows what behaviuor can occur and what error can be expected when the application does not have proper permissions.

I. Custom permissions created by app:

Global: The Scheduler: Access.
Project: The Scheduler: Use.

1 1. App’s global permission: The Scheduler: Access.
2 2. App’s project permission: The Scheduler: Use.
3 1. Browse Projects.
4 2. Create Issue.

1. App’s global permission: The Scheduler: Access.

Jira Settings → Global Permissions → The Scheduler: Access

If in Jira settings there will be lack of The Scheduler: Access permission, the missing permissions banner should be visible above the Scheduled Issues table.

2. App’s project permission: The Scheduler: Use.

Project Settings → Permissions → The Scheduler: Use

The same situation as in case of absence The Scheduler: Access permission: if in Jira settings there will be lack of The Scheduler: Use permission, the missing permissions banner should be visible above the Scheduled Issues table.

II. Project permissions required for users:

Browse Projects.
Create Issues.

1. Browse Projects.

Project Settings → Permissions → Browse Projects

The same as in Cloud version - in Data Center/Server app version, without Browse projects permission users can not access projects, thus cannot access The Scheduler.

2. Create Issue.

Project Settings → Permissions → Create Issue

If in Project settings there will be lack of Create Issue permission, the missing permissions banner should be visible above the Scheduled Issues table.

Examples of applied permissions