nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Auto-assignment with multiple components

Ben_e5wk9p

I have created 3 components. For these 3 components I have specified the "Component Lead" as the "Default Assignee" and for all 3 components I have also defined one person as the "Component Lead". See:

Bildschirmfoto 2022-09-12 um 11.52.46.png

My question now relates to what happens when an "Issue" is created for which all 3 components are selected.

For help, I found this page https://confluence.atlassian.com/adminjiraserver/managing-components-938847187.html#Managingcomponents-default_assignee
There it says:

"If an issue has multiple components, and at least one of them uses Component Lead, then the Component Lead takes precedence over Project Lead, Project Default, and Unassigned as the Assignee. If the components have different Component Leads, the default assignee will be set to the Component Lead of the component that is first alphabetically."

Now I create an issue, select all 3 components and leave the "Assignee" field blank:

Bildschirmfoto 2022-09-12 um 11.55.49.png

I would assume that the issue is assigned to JENS, but the issue is assigned to the TEST USER instead. See:

Bildschirmfoto 2022-09-12 um 11.56.04.png

Can anyone help me with this? Did I do a mistake or is Jira wrong? I don't see where I made a mistake (?). I have observed this behavior on several sites and don't know why.

Kind regards,

Ben

Accepted answers

Alex Koxaras -Relational-

Hi @Ben

Has Jens a last name? If yes, from what letter does it start?

All comments

Alex Koxaras -Relational-

Hi @Ben

Has Jens a last name? If yes, from what letter does it start?

Alex Koxaras -Relational-

And in addition, do all of your user has the assignable user permission? Can they be assigned?

Rilwan Ahmed

Hi @Ben ,

I too noticed it now. Jira is taking the ID of users and sorting it instead of the display names.

You can click on the names and you see the user ID (its alpha numeric)

Ben_e5wk9p

Hi @Alex Koxaras -Relational- ,

thanks for your answer. Yes, all user have the assignable user permission . I think the last name of the User is not relevant. The alphabetical order is related to the component, not the User (as I understand it).

Ben_e5wk9p

Ok, but shouldn't Jira sort it alphabetically according to the COMPONENT, not the component lead?

Alex Koxaras -Relational-

@Ben

A component default assignee will override the project's overall default assignee. If someone creates an issue with more than one component, and the default assignees for those components are different people, then Jira assigns the issue to the default assignee of the component that was created in the system first.

https://support.atlassian.com/jira-software-cloud/docs/organize-work-with-components/

Leandro Azevedo_ocwl4l

https://community.atlassian.com/t5/Training-Certification-questions/Re-Re-ACP-120-Course-Material-amp-Sample-Paper/qaq-p/2188932/comment-id/1384#M1384

Leandro Azevedo_ocwl4l

I suggest to take a look at this discussion here : https://community.atlassian.com/t5/Training-Certification-questions/ACP-120-Course-Material-amp-Sample-Paper/qaq-p/2187471#M1451 in the post of Tauwa at Nov 11, 2022 , where it says that "The solution given by the agile experts is that the assignment is based on the id of the component and in fact I have tested it and the explanation is correct. The component with the first (lowest) Id will win."

Carolina Castro_qfpw3a

I believe that, in terms of the ACP-620 test, this is still a mistery.

One of the Atlassian documents is easy to understand and makes sense (Managing components), then they provide the same information in another page (How to Manage Components and Default Assignees in Jira Software Projects) with example #5 that don't make sense.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

component

jira-service-management-cloud