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; } } }

having 3 component leads, the issue assignee isn't assigning alphabetically

Aishwarya Rajendra

I have created 4 components namely- Architecture, Database, Software, Hardware. And have assigned 4 users as component leads in jira software cloud. According to the jira documentation, the assignee has to be taken alphabetically--

{cloud doc : 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 is first alphabetically.}

But its not taking the assignee as per alphabetical order

Accepted answers

Nic Brough -Adaptavist-

It probably is searching alphabetically, but not on the display or even login. When the doc was first written, it used to be that your login id was stored as the identifier, but now it's an apparently random string. I'd guess that it is still doing the alphabet sort, but the content is now random so there's no apparent order to it!

Yong Yang

In JIra Cloud, we can copy the fields values from the sub-tasks' parent issues when creating new sub-tasks through the workflow postfunction of create issue post fucntion.

All comments

Walter Buggenhout

Hi @Aishwarya Rajendra,

Cloud and server are different products and may/do differ in behaviour. Reference the Cloud documentation which does not have the same level of refinement as on server instead.

So in short: the server documentation does not apply to cloud.

Nic Brough -Adaptavist-

Aishwarya Rajendra

Hello @Walter Buggenhout ,

Here is what the cloud documentation says-

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 is first alphabetically.

Aishwarya Rajendra

Oh okay! Thanks a lot!! @Nic Brough -Adaptavist-

Ganesh Babu_l9dxny

Hey @Nic Brough -Adaptavist-

I am bit confused on the login id storage (earlier as a identifier, now a random string) explanation here,

When the doc was first written, it used to be that your login id was stored as the identifier, but now it's an apparently random string. I'd guess that it is still doing the alphabet sort, but the content is now random so there's no apparent order to it!

Can you please help me understand on the same..

And also do you mean to say that, suppose if i have 4 components chosen for an issue,

Example: Architecture, Database, Web Dev, UI/UX Design are the components, ideally/technically it should chose the assignee as the component lead of the component Architect. But in this case which is not working like that.

In the last line you mention, the content is now random, so will it not work in the order and chose the assignee as the one whose component is alphabetically first?

I could also see one weird operation which is happening

If i create a project, and create the components for the first time namely DB, UI/UX Design, Web Dev. And Create the issue in the project with all three components chosen will work as expected, i.e. the Component Lead of DB is going to be the assignee.
As the next step in the same project, if create a new component as App Dev. And now if create the issue by chosing all the four components. The expected behaviour is too assign the issue for the component lead of App Dev. Where its assigning the issue for the component lead of DB.
My observation here is any component which is created for the next time, even if the alphabetic order of the issue is having the precedence. It is considering the earlier precedence of the components and assigning it to the same lead.
The above operation looks like a bug for me.

Thanks and Regards,

Ganesh Babu J

Nic Brough -Adaptavist-

The alphabetic order is done on the user id, not the component.

Allison Stewart_nejvgh

I'm finding the same issue. I have multiple components with different assignees. When I choose several components, in any order, the system is not assigning to the lead from the first component alphabetically. It is actually assigning the issue to the lead who's username is first alphabetically.

That's what I'm finding in my testing. It is possible that it's doing this based off userID as well, but I can't tell that for sure.

Is there any way to change the assignment logic?

Yong Yang

In JIra Cloud, we can copy the fields values from the sub-tasks' parent issues when creating new sub-tasks through the workflow postfunction of create issue post fucntion.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software-cloud

jira-cloud

jira-server

atl-gruland