Jira custom fields: best practices and when to use validation

Custom fields are one of the most abused features in Jira. Here's how to keep them clean, validated and actually useful.

Every Jira instance eventually accumulates hundreds of custom fields. Most unused, wrongly configured, or duplicated.

The golden rule: Only create a custom field when a standard field genuinely cannot do the job.

Common mistakes:

• Project-specific fields instead of context restrictions
• Free-text fields where a select list would be cleaner
• No validation on fields that feed automation or reporting

When validation matters. If a custom field is used in JQL queries, automation conditions, SLA calculations, or external integrations — enforce a format. Free text breaks all of these eventually.

RegEx use cases: contract numbers, version strings, cost codes, department codes.