To ensure that newly created issues in a company-managed project’s Kanban board are not left unassigned, you must configure theDefault Assigneesetting in the project’s settings. TheProject lead(Option B) is a valid and appropriate choice, as it assigns new issues to the project’s designated lead by default.
Explanation of the Correct Answer (Option B):
In a company-managed project, theDefault Assigneesetting determines who is automatically assigned to new issues when no assignee is specified during creation (e.g., when creating issues directly on a Kanban board). TheProject leadis a predefined user set in the project’s settings and can be selected as the default assignee to ensure issues are not left unassigned.
By selectingProject leadin theDefault Assigneedropdown, all new issues created in the project, including those created on the Kanban board, will be automatically assigned to the project lead, meeting the requirement.
Exact Extract from Documentation:
Configure the default assignee
TheDefault Assigneesetting in a company-managed project determines who is assigned to new issues when no assignee is specified.
Options include:
Project lead: Assigns issues to the user designated as the project lead.
Unassigned: Leaves issues unassigned (if allowed by the project’s permission scheme).To configure:
Go toProject settings > Details.
SelectProject leadin theDefault Assigneedropdown.Note: Ensure the project lead has theAssignable Userpermission in the project’s permission scheme.(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")
Why This Fits: SelectingProject leadensures that all newly created issues are automatically assigned to the project lead, preventing them from being unassigned, making Option B the correct answer.
Why Other Options Are Incorrect:
Board administrator (Option A):
There is noBoard administratoroption in theDefault Assigneedropdown. Board administrators manage Kanban or Scrum boards but are not a predefined assignee role for issues.
Extract from Documentation:
TheDefault Assigneedropdown includesProject lead,Unassigned, or specific users, but notBoard administrator.
(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")
Component leads are assigned to issues only when a component with a default assignee is selected. They are not part of theDefault Assigneesetting.
(Source: Atlassian Support Documentation, "Manage components in Jira Cloud")
TheDefault Assigneesetting does not includeProject admin. UseProject leadorUnassigned.
(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")
Reporter (Option E):
TheReporteris the user who creates the issue and is not an option in theDefault Assigneedropdown for company-managed projects. Assigning issues to the reporter would require a custom automation rule or manual assignment, not a default setting.
Extract from Documentation:
TheReporteris not a valid option forDefault Assignee. UseProject leadorUnassignedfor automatic assignments.
(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")
Additional Notes:
TheDefault Assigneesetting is configured inProject settings > Details, requiringproject adminprivileges.
Ensure the project lead has theAssignable Userpermission in the project’s permission scheme to be eligible as an assignee.
IfUnassignedis selected, issues could remain unassigned, which violates the requirement.
[:, Atlassian Support Documentation:Manage project settings in Jira Cloud, Atlassian Support Documentation:Manage components in Jira Cloud, Atlassian Support Documentation:Manage permissions in Jira Cloud, ]
Submit