How to enforce single component per ticket?

[Jordan Hubbard]

We live in a world where multiple components per ticket is like multiple inheritance in C++ - a fine concept until you actually USE it, then you realize you're an idiot and everyone who inherits your work will share this opinion.

We need to turn multi-component assignment behavior OFF.  How to do this?

[James Tome]

@Jordan Hubbard I agree with you that we should have the option to limit the Component field to one value.

I'm trying to drive the adoption of the Components field and the Default Assignee functionality built into this system field in our organization.  If Components can have multiple values, then I'm not certain which of my colleagues will become the Default Assignee.

This seems like an oversight by the Jira product team.

@Nic Brough -Adaptavist-—Your workaround is valid if the use of Default Assignee (and Component Lead) is not critical to the organization. In my case, those are important, so your workaround isn't viable.

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

You can't do this on Cloud (there's a code tweak you can make to Server/DC that converts the field to a single select on the front end, but it won't stop people using the REST API or apps to set multiple values)

Your best bet is probably to create a single-select custom field with your component list in it.