HelzUnison: Duplicate Custom Field Prevention for Jira
Check for duplicate custom fields before you create one.
Every long lived Jira instance accumulates "Customer Number", "Customer No" and "Cust Number", each created by someone who looked and did not find the existing one. Unison puts the check at the point of creation, where it costs nothing.
Getting started
- Open Apps › Unison: Custom Fields.
- Type the field name you are about to create.
- Choose a field type, then select Check only or Create field.
How matching works
Names are normalised before comparison rather than compared literally: lowercased, # expanded to "number", punctuation reduced to separators, known abbreviations expanded, and naive plurals folded. So "Cust No" finds "Customer Number".
How results are scored
Scoring weights name similarity most heavily, then field type compatibility and description similarity, and normalises over the signals actually available so a missing description does not penalise an otherwise perfect match. Results are ranked and labelled, with Very likely duplicate at 90 and above and Strong potential match at 75 and above. Every match shows which signals fired and how much each contributed.
Looking at a candidate
View details shows an existing field's type, contexts, and which projects and screens use it, so you can judge whether it genuinely covers your case.
Creating the field
When you are satisfied the field is new, create it from the same screen with its type and description. Every create runs the duplicate check first. Unison never edits or deletes an existing field.
Administrator settings
Site administrators can set an accent color used for buttons and highlights.
Permissions and data
Unison reads your custom field inventory, field configurations and contexts in order to compare a proposed name against existing fields, and requests manage:jira-configuration because creating a custom field requires it. That permission is used only to read the inventory and to create a field an administrator explicitly asked for. Comparisons are computed on request and not stored. The app declares zero external network egress.
Support
Questions or problems: support@helzbrand.com