I don't see a reason why we are allowed to create a duplicate custom field with same name. Can we log a support ticket to JIRA not to allow the field creation if field with same name (custom or default) already exists? It creates a confusion while selecting the field for reports etc.
I completely support this idea.
I've witnessed a JIRA instance with up to 33 custom fields with exactly the same name, which is a mess both for coding, referencing in post-functions, and searching through the issue navigator.
The reason? They didn't know of the existence of contexts, nor thought of the consequences of having multiple fields with the same name.
Things can go even worst when custom field names replicate system fields...
An older version of Jira used to prevent admins adding or renaming fields to have the same name as existing fields. You could work around it by doing imports and selecting "new fields", but generally it was really helpful in stopping admins doing bad things.
It was really annoying when that was dropped and duplicates allowed, I never found out who made that silly decision.
Thanks all for feedback.
Logged JIRA ticket for this issue
I'm a bit dissapointed that it's been almost two years and still no resolution to your worry.
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Jira Administrator
Configure Jira Software, Jira Core, or Jira Service Management, including global settings, permissions, and schemes.
Managing Jira Projects Cloud
Learn to create and configure company-managed projects in Jira Software and partner effectively with Jira Admins.
Learning Path
Become an effective Jira Software Project Admin
This learning path is designed for team leaders who configure Jira Software projects to match a team's processes.