How to make the system Component field as single select item without any add-on plugin?

[Sagayaraj David]

The system field Component has a default assignee based on the Component field value selection during Create Issue. Because this field is mutli-select field, the default assignee field makes no meaning. Moreover I want to have another select field values based on the Component field value selection? How to set the Component field as single select instead of default behaviour multi-select?

[Mitchell Davison [EY]]

Hi Sagayaraj,

I don’t believe this is possible, certainly without an add-on. Using ScriptRunner you could write a scripted Validator that checked to see the field had only one value set in it on a transition.

[Sagayaraj David]

In my opinion, Atlassian should provide it as Single Select or Multi-Select (if dont want to disturb existing behaviour) as choices for user to choose from. Only then it makes sense to provide Default component lead (for single select). And, Script Runner is not free for modifying the default behaviour.

[Nic Brough -Adaptavist-]

The point of the components field is to tag items in a project with all the areas of the project it might affect.  So it needs to be a multi-select.

[Erik Pauli]

@Nic Brough -Adaptavist-That's wrong in my opinion, because then the component-lead is useless. How would you build up a portfolio product approach with several different people responsible for the same issue in a backlog with more than thousand issues?

[Nic Brough -Adaptavist-]

Eh?  That's not what the component lead is for.  The person responsible for dealing with an issue is the assignee, not the component lead.

The component lead is the person who has responsibility/expertise/resource for working with the component, not the issue.

[Erik Pauli]

It is not about dealing with a single issue, it is about the responsibility and expertise of certain parts of the backlog with hundreds of issues as you said. And especially therefor a lot of people are using it in combination with Dashboards, Filters (like "component in componentsLeadByUser()") and a lot more.

You are free to suggest a better workaround for product discovery purposes - until Jira Product Discovery is hopefully offering better possibilities.