Overriding the validation of custom fields

We have seen how to write a custom field and set its options programmatically. We also discussed how the value set on a multivalued custom field is validated against its set of preconfigured options. If the value doesn't belong to it, the validation fails and the issue can't be created or updated.

But what if we have a scenario where we need to suppress this validation? What if we need to add values to an issue that don't come from its preconfigured options? Normally, you would add this to the options programmatically, as we've seen before, but what if we don't want to do this for some reason? This is just one example of when you can suppress the validation in your custom field.

Getting ready

Create your custom field, as we saw in the first recipe of this chapter.

How to do it...

All you need to do here is to suppress the validation happening in the original parent custom field if you are extending an existing custom field type such as MultiSelectCFType...