Hey, this is a pain point I see all the time with team-managed projects. Since custom fields there are project-scoped, you can't just merge them through the UI like in company-managed ones. Here's what works: first, pick which field name/version you want to keep as your canonical one. Then go issue by issue and reassign the data using bulk edit (you'll need to map old field values to the new one manually or via a script). Once all issues point to the single field, delete the duplicates.
The real fix though is prevention, before any migration or import, do a field mapping audit so you're not creating duplicates in the first place. Tools like 'Migration Field Cleanup' can also flag potential field duplicates which saves hours of manual cleanup.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.