Boris is reviewing his assigned issues.

To move issues from the backlog to a planned sprint in a Jira Software Cloud project, Boris needs permissions to modify the issue’s sprint field and edit the issue itself. The two permissions required areSchedule Issues(Option B) andEdit Issues(Option D).

Explanation of the Correct Answers:

Schedule Issues (Option B):

TheSchedule Issuespermission allows a user to add issues to a sprint, remove issues from a sprint, or move issues between sprints. This permission is necessary to move issues from the backlog (which is not part of a sprint) into a planned sprint.

Exact Extract from Documentation:

Schedule Issues permission

TheSchedule Issuespermission allows users to:

Add issues to a sprint.

Remove issues from a sprint.

Move issues between sprints or to the backlog.This permission is required to manage the sprint field in issues, such as moving an issue from the backlog to a planned sprint.Note: This permission is granted via the project’s permission scheme.(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")

Why This Fits: Moving an issue to a planned sprint involves updating theSprintfield, which requires theSchedule Issuespermission.

Edit Issues (Option D):

TheEdit Issuespermission allows a user to modify issue fields, including theSprintfield. Without this permission, Boris cannot edit the issue to set its sprint, even if he has theSchedule Issuespermission.

Exact Extract from Documentation:

Edit Issues permission

TheEdit Issuespermission allows users to modify issue fields, such as Summary, Description, or Sprint. This permission is required to update an issue’s details, including moving it to a sprint if combined with theSchedule Issuespermission.

Note: This permission is granted via the project’s permission scheme.

(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")

Why This Fits: Editing theSprintfield to move an issue into a planned sprint requires theEdit Issuespermission, as it involves modifying the issue’s metadata.

Why Other Options Are Incorrect:

Work On Issues (Option A):

TheWork On Issuespermission allows users to log work on issues (e.g., record time spent). It is not related to moving issues to a sprint or editing issue fields.

Extract from Documentation:

Work On Issues permission

Allows users to log work on issues using the time tracking feature. This does not include editing issue fields or managing sprints.

(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")

Move Issues (Option C):

TheMove Issuespermission allows users to move issues between projects or change their issue type within the same project. Moving an issue to a sprint does not involve changing its project or issue type, so this permission is not required.

Extract from Documentation:

Move Issues permission

Allows users to move issues to a different project or change their issue type. This is not required for moving issues to a sprint within the same project.

(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")

Manage Sprints (Option E):

TheManage Sprintspermission allows users to create, start, complete, or delete sprints. While this permission is necessary for managing the sprint itself, it is not required to move issues into a planned sprint, as Boris is not creating or modifying the sprint.

Extract from Documentation:

Manage Sprints permission

Allows users to create, start, complete, or delete sprints. Moving issues to an existing sprint requires theSchedule IssuesandEdit Issuespermissions, notManage Sprints.

(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")

Assignable User (Option F):

TheAssignable Userpermission allows a user to be assigned to issues (i.e., set as the Assignee). It does not affect the ability to move issues to a sprint.

Extract from Documentation:

Assignable User permission

Allows users to be set as the assignee of an issue. This does not include editing other fields like the Sprint field.

(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")

Additional Notes:

Boris likely already has theBrowse Projectspermission, as he can review his assigned issues. TheSchedule IssuesandEdit Issuespermissions are specifically required for the action of moving issues to a sprint.

These permissions are granted via the project’s permission scheme, which can be checked inProject settings > Permissions.