No Assignee vs Unassigned Components

[Samuel Westen]

Documentation states that the default assignee hierarchy is - 

Component Lead > Project Lead > Unassigned > Project Default


The conditions for which the "Project Default" option is set as the assignee for an issue is "if an issue has multiple components, and no assignee is selected for any of the components, we use the Project Default assignee."

Is "no assignee" different from "unassigned" in the context of Component default assignee's ?

[Antoine Berry · Accepted solution]

Hi @Samuel Westen ,

As per my testing, your hierarchy is correct.

No assignee should be the same as unassigned. If you look at the documentation, if you select only components which have "Unassigned" or "Project Default" as default assignees, and at least one of them has "Unassigned" as default, then the assignee field will remain empty.

[Samuel Westen]

Thanks for the confirmation Antoine.

This confirms that the conditions stipulated in the documentation for "Project Default" becoming the Default Assignee for a group of components on a single issue is incorrect and cannot be achieved.