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 ...

Get JIRA Development Cookbook - Third Edition now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.