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

Components default assignee clashing

Javier Cárdaba

I am reviewing "Managing components" section (https://confluence.atlassian.com/adminjiraserver073/managing-components-861253335.html).

Talking about "Selecting a Default Assignee", it is said: "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."

The question is: if an issue has 2 components (one with "Unassigned" default assignee and one with a specific person).... will they clash?

Bonus question: which addons you recommend to enable more functionality on assigning issues based on components?

Thanks!

Accepted answers

All comments

Jack Brickey

No. If one component is unassigned there should be no collision. Easy to test and verify.

Sorry, I can’t help on the bonus question. Do you have some specific requirement. Might not need an addon.

unknown

Hi @Javier Cárdaba,

Tested your question;

The question is: if an issue has 2 components (one with "Unassigned" default assignee and one with a specific person).... will they clash?

The result was the issue was left unassigned.

If you require a more detailed aspect to Components my suggestion would be to trial: https://marketplace.atlassian.com/apps/1211548/subcomponents-and-component-versions?hosting=server&tab=overview

Hope this helps

Jack Brickey

Danny, interesting for sure. i would not have guessed (obviously :-)) that! Unassigned is the same as empty so that wouldn't be the way I implemented.

Javier Cárdaba

Hello @[deleted]. In fact we are using the Cloud AddOn: https://marketplace.atlassian.com/apps/1214373/subcomponents-for-jira-cloud?hosting=cloud&tab=overview

We have built a hierarchy to work the following way:

Ticket is created assigning the fist level component (1st level of support).
A dedicated group assigns the correct child (2on level of support).
Only the child components have named assignee. The first level are configured to leave the ticket unassigned.

I am not able to see how this addon is helping me in this targeted behaviour. Thanks in advance!

Javier Cárdaba

Thanks @Jack Brickey for your reply. Which approach would you use?

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration