We all deal with priorities every day, your task view or Jira board, invites you to categorize all items into low, medium or high priority. What Jira got wrong ist the introduction of "priority urgent" as a result of folding the two-dimensional Eisenhower method into a dropdown list.

The challenge with "must fit in a dropdown" is that classifying task priority is only a prelude, a clarification, a segmentation of what we actually do, explicit or implicit:

Priorities are not classified, they are ranked

You followed Ike and ended up with 20 tasks that are equally important and urgent. Equally? Nope. We all rank them using whatever additional properties we have at hand in our plan of execution.

objects in real life are complex with many optionalities (my spell checker claims that isn't a word), that leave their imprint on their digital twins. To avoid exposing endless list of parameters you can use the builder pattern described by the GoF. It is the digital version of

This is what I know, let's work with that

You might want to go with the flow, and just pick a size and for the rest pick what everyone else is picking. The builder pattern does both gracefully.

Ring r1 = Ring.builder().size(9)build();

Ring r2 = Ring.builder()
              .material(Material.PLATINUM)
              .size(9)
              .diamonds(3)
              .carats(0.75)
              .engraving("forever")
              .build();

or if Rust rocks your boat

let r3 = RingBuilder::builder()
                     .material(Material::Platinum)
                     .size(9)
                     .diamonds(3)
                     .carats(0.75)
                     .engraving("forever")
                     .build();

So I was wondering what it would take using defaults from a configuration file instead hard coding them in the builder.