Jira admins can't identify custom fields when names are duplicated

Everything in Jira boils down to the ID, this is a pain we have also felt. Jira doesn't care what you name the thing, and before I was an admin the custom field ID was my biggest pain point.

Because client said "I want this field to be called 'Team'". And it is 100% allowed in Jira. They design custom fields to be able to have the same name. And it's stupid that Jira interface to select custom fields conveniently forget that fact and only give you the name. And it would take 10+ years for Atlassian to fix this.

ID would help if they stop trying to hide it so much. Previously custom field id is in the URL only, now you can find it in a few more places but not most. Sometimes user request the same field name be used for two custom fields in different tabs. They want it because that's how it was on their old platform. When your system allows fields with same name in same space, but your system also only show the name when you have to select a field. Contradicting yourself. This problem also extends to JQL. You end up needing to use cf[#] instead of name because fields can have same name. Which the system itself tries hard to not show you to number. Jira's punching itself black and blue with its own fists.