Dropdown Custom Fields are here!

[#1]

What happens when a custom field... is too custom? 

Sometimes, it's great when your team can enter their own field values. Sometimes it's not a preset list. But when you are dealing with compliance, or finance, or sales, or really any topic that requires analysis, it's helpful to have your team pick from a standardized set of options instead. 

Announcing, Dropdown Custom Fields! 

We have recently shipped a new custom field type that allows you to enter options at setup, and your devs can either select a single or multiple options. Simple as that! (Yes, it works with config-as-code too.) 

Check out some more examples below, and let us know how you'll use the dropdown. What would you like to see next?

[Garyl Paras]

Any plans on adding this to the scorecards and filters? Thanks!

[Patrick Hill]

Thanks @Garyl Paras We'll be adding Scorecard criteria and filters for this in component search in the future - we'd love to hear how you'd want to utilise criteria for these fields, or in filters when searching for components.

[shall]

@Patrick Hill I was just looking for the feature @Garyl Paras is talking about. I'd like to use Scorecards to ensure certain dropdown fields are filled in, but this does not seem possible at this time.

I would use filters with to check dependencies by our dropdown field selection.

[Ben Krig]

We recently revisited this feature and shipped functionality so that you can filter by dropdown custom fields directly in the UI!

Check out https://community.atlassian.com/t5/Compass-articles/Search-and-filter-your-components-with-dropdown-custom-fields/ba-p/2693884 for more details!