Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

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

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?

1 answer

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.

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.

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.

@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?

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.

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.

Suggest an answer

Log in or Sign up to answer

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