Unison: Duplicate Custom Field Prevention for Jira

Every long lived Jira instance ends up with "Customer Number", "Customer No", "Cust Number" and "customer_number", each created by someone who looked, did not find the existing one, and moved on. The cost lands later: a custom field limit you cannot get under, slower indexing, and reports that quietly disagree.

Unison puts a check at the point of creation. Type the field name and it scores your proposal against every existing custom field using normalised names: abbreviations expanded, punctuation stripped, plurals folded, so "Cust No" finds "Customer Number". Scoring weights name similarity, field type compatibility and description similarity, and every match shows which signals fired.

When the check comes back clean, create the field from the same screen with its type and description. The safe path and the fast path are the same path, which is how a governance step survives a deadline. Unison never edits or deletes an existing field, and declares zero external network egress.