Ahmed is a project administrator in the DEV project, which means he is in theAdministratorsproject role (as per the permission scheme, whereAdminister Projectsis granted to this role). However, he cannot create sprints because he lacks theManage Sprintspermission, which is granted to theatlassian-addons-project-accessandCoreproject roles. To resolve this, Ahmed shouldadd the Administrators project role to the ‘Manage Sprints’ permission(Option D).
Explanation of the Correct Answer (Option D):
TheManage Sprintspermission allows users to create, start, complete, or delete sprints in a project. According to the permission scheme, this permission is granted to theatlassian-addons-project-accessandCoreproject roles, but not to theAdministratorsproject role, which Ahmed belongs to.
As a project administrator, Ahmed has theAdminister Projectspermission, which allows him to modify the project’s permission scheme (viaProject settings > Permissions) and add theAdministratorsproject role to theManage Sprintspermission. This will grant him the ability to create sprints without needing Jira administrator privileges.
Exact Extract from Documentation:
Manage Sprints permission
TheManage Sprintspermission allows users to create, start, complete, or delete sprints in a project. This permission is granted via the project’s permission scheme.
To update permissions:
Go toProject settings > Permissions.
Edit the permission scheme and add a user, group, or project role (e.g., Administrators) to theManage Sprintspermission.Note: Project administrators can modify the permission scheme for their project if they have theAdminister Projectspermission.(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
Why This Fits: Adding theAdministratorsproject role to theManage Sprintspermission directly addresses Ahmed’s lack of permission to create sprints, leveraging his existing project administrator privileges.
Why Other Options Are Incorrect:
Add himself to the Core project role (Option A):
Adding himself to theCoreproject role would grant Ahmed theManage Sprintspermission, as this role is listed for that permission. However, as a project administrator, Ahmed can modify the permission scheme directly instead of adding himself to another role, which may grant unnecessary permissions (e.g.,View Development Tools). Option D is more appropriate, as it aligns with his administrative role.
Extract from Documentation:
Project roles are managed inProject settings > People. Adding a user to a role grants all permissions associated with that role, which may include more than needed.
(Source: Atlassian Support Documentation, "Manage project roles")
Permissions are granted to specific roles or groups in the permission scheme. Verify the roles assigned to each permission before adding users.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
TheView Development Toolspermission grants access to development information, not sprint management.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
Additional Notes:
Ahmed’s ability to modify the permission scheme depends on hisAdminister Projectspermission, which is confirmed by his role as a project administrator.
Theatlassian-addons-project-accessrole is typically used for system or app-related permissions and is not relevant for Ahmed to modify.
After adding theAdministratorsrole toManage Sprints, Ahmed and other administrators will gain sprint management capabilities.
[:, Atlassian Support Documentation:Manage permissions in Jira Cloud, Atlassian Support Documentation:Manage project roles, Atlassian Support Documentation:Manage sprints in company-managed projects, ]
