Permissions

Creating a schedule

Changing a schedule

Edit, pause, resume and delete: the owner or a Jira administrator.

What you see

You see the schedules of projects you can browse. Jira administrators see what their own project access allows in the lists, and everything in the administration page’s error list and log.

Reassigning the owner

If the owner leaves, is deactivated, or loses access, issue creation fails (see Errors). A Jira administrator opens Administration, Schedules in error, Reassign owner, searches a user, and picks one. Only users who can create issues in that project are offered. New issues are created in the new owner’s name.

Permissions RepeatWise asks Jira for

Read and write Jira work (to create, comment on, transition and search issues as the owner), read users (for the owner picker, run as the admin), and read projects. Jira Software sprint read and write, and board read, are used to add new issues to a sprint. Jira Service Management request read and write are used to list request types and raise service requests as the owner. The manifest has no external scope. See Data and privacy.

After an app update

When an update adds permissions, each user may be asked to Allow access once. The schedule owner must do this for their schedules to keep running. Until then, issues cannot be created as the owner and the schedule shows an error (see Errors).