Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to add the new entity like Components (aka Components#2)


Hello, I need to add one more field like Component, is it possible to do it with project settings?

There is image below as the result I need. The second entity like Component is Brand. There is no relation or dependence between Component and Brand. Just one more field with properties like Component.


1 comment

Welcome to the Community!

No, there's no field type like Component, it's a single system field with load of functionality layered over it.

The closest you can get would be to ask your admins to add a "Multi-select list" into the system and associate it with your project(s).  These are similar to components in that you can put many of their options on to an issue, but only Jira admins can maintain the list of options, there's no component lead functions and no dedicated reporting.

Like Natalie Kim likes this

Hello, thank you for your answer.

I create the custom field, but it is not clickable as components or labels.

Is it possible to have clickable multi select field as Component with limited list of options?



Log in or Sign up to comment