Multiple components and default assignees

[Esther Strom]

So this isn't something that needs to be solved; it's just a question I've had for a while. 

Part of the reason for using components is to allow more granular default assignments, correct? You have a default assignee on the project level, and then can break it down further by adding components. 

Say I have ComponentA and ComponentB, each with a different default assignee. Given that Jira allows us to add multiple components to an issue, how does it decide which component "wins" as far as automatic assignment goes? And for that matter, why would the system even allow multiple components to be added if it could result in a race condition for assignment?

[Dave Theodore [Coyote Creek Consulting]]

It doesn't result in a race condition.  The first Component value added wins. In your example, it would be ComponentA.

[Jonathan_nor]

The most specific takes precedence over the others, as stated in the official documentation:

Multiple components and selecting assignees

In the case of issues with multiple components, the assignee structure works top-down, that is from the least to the most specific. The most specific (Component Lead) takes precedence over others. For example, if an issue has multiple components and some of these components have the Unassigned option selected, some have a Project Lead specified, and some others - a Component Lead, then the Component lead will always take precedence as the Assignee. 

https://confluence.atlassian.com/adminjiraserver/managing-components-938847187.html