Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The Scheduler for Jira Cloud

...

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.
Permissions:

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

1b. Browse project permission.

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

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

...

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

(error)

(error)

(error)

(tick)

(tick)

(error)

(tick)

(tick)

Table: 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.

...

User

Addon

Atlassian addon permission

Result of lack/grant permissions on screen

(error)

(error)

(error)

(error)

(error)

(tick)

(error)

(tick)

(error)

(error)

(tick)

(tick)

(tick)

(error)

(error)

(tick)

(error)

(tick)

(tick)

(tick)

(error)

(tick)

(tick)

(tick)

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

The Scheduler for Jira Data Center (and Server)

[tbc]

What are the types of errors to be expected when some global/project permissions is missed in settings of Data Center and Server projects? Examples of this are below.


I. Custom permissions created by app:

  1. Global: The Scheduler: Access

  2. Project: The Scheduler: Use

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:

  1. Browse Projects

  2. 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.

  1. Create Issues

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.

...