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

Wrong assignee by component

unknown

Usually I choose the components to a task by priority. If I create the task, Jira sorts the components by alphabet and sets the assignee of the component, that's first in the alphabet, and not the one of the first selected component.

Is there a way to configure that properly? Or might this be a bug?

Accepted answers

unknown

Thanks for help. See

https://jira.atlassian.com/browse/JRA-32858

I put a little more focus on my question "alphabet vs. priority".

All comments

Ramiro P

Hi, as you can read in this documentation:

https://confluence.atlassian.com/display/JIRA052/Defining+a+Component#DefiningaComponent-SelectingaDefaultAssignee

(info) If an issue has multiple components, and the default assignees of components clash, the assignee will be set to the default assignee of the component that is first alphabetically.

So this is not bug, it looks like it's meant to be that way. Maybe there's a way doing some development but haven't found something like that yet.

Hope this helps.

Ramiro P

Here's an Issue created for this: https://jira.atlassian.com/browse/JRA-3762

unknown

Thanks for help. See

https://jira.atlassian.com/browse/JRA-32858

I put a little more focus on my question "alphabet vs. priority".

Welcome!

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

Quick Links

Find more posts tagged with

jira

assign

component