It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Components default assignee clashing

I am reviewing "Managing components" section ( 


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?



2 answers

0 votes
Jack Community Leader Jun 19, 2018

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. 

0 votes
Deleted user Jun 19, 2018

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: 

Hope this helps

Jack Community Leader Jun 19, 2018

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. 

Hello @[deleted]. In fact we are using the Cloud AddOn:


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!

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

Jack Community Leader Jun 19, 2018

Not exactly sure w/o fully understanding your environment and process but here is something that comes to mind.

the issue here is that Components field can have more than one entry. So your could enforce a process where the user needs to replace the current component w/ a new one. This likely won't work all of the time given humans are involved. 

Another approach:

Create a custom field (drop down single select) to replace what you are trying to do w/ component. It can default to '1st level of support' or whatever. Users would be required to update the field just like they would add a component to pass the issue off. Add automation using something like Automation for Jira or even the Lite version that would reassign the issue whenever the custom field is updated.

I think that is where I would start based upon what i'm reading here.

Just as a point of interest, I just tested this on our Jira Cloud instance and got the opposite result. 

Created: Issue with two components, one with an unassigned default and one with an assignee.

Result: never unassigned, regardless of component alphabetical order. Always goes to the named assignee.  

If both components have named assignees the alphabetical component ordering is honored. 

Like # people like this

I tried this out too and got the same result. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

303 views 1 3
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you