7c134b43cfa4: The EXACT thing Judy explained happened in my org a couple months ago. Another example, someone created a custom field named "Rank" so every filter in the company that was set up to "ORDER BY Rank ASC" no longer had a valid rank field. Every Board in the company that used stack ranking (hundreds of them) stopped being able to drag and drop tickets to change priority order.

This ask will eliminate my ability to "replace" a field with the same name but a different field type; so, hopefully, if this change ever goes into effect, it will take this use case into account. 

7c134b43cfa4  This happened to us back in July when someone added a custom field called 'Team' in a team managed project in Jira. It not only caused issues in Jira with filters etc, but broke several automation rules in Jira Service Management.  We spent a lot of time finding and fixing everything. As this happened so long ago, I don't have any rule audit logs or screenshots I'm afraid. 

Hi 702354a3bd24 , 093ff76bd2b6 , could you provide more details on your situation where existing filters and automations has been broken just by adding duplicated name in some team managed project, please?

Looking at all "closed" issues (stories, bugs) related to the same issue. It is weird that it i still not solved.

This is such a basic thing to have! Why has this ticket not been acted on - open since 2017? Worst thing is a team managed project enables the project admin to add a custom field without the ability to see if a field with the same name exists. That duplicate field then breaks automations and filters in the whole of Jira/JSM, not just the project it was created for.

This bug strikes again, ruined dozens of filters we rely on for releasing product to the field because an admin in a completely unrelated (team managed no less) project created a field with the same name....

My workaround is to put the project key in parentheses after EVERY custom field. Looks bloody ugly and seems to do a great job of confusing non-admins.. but it works.

Really confusing for my team working with a very high loaded (and our most important) project in Jira to see suddenly different default options just because another unrelated project is using the same field ("Market") - We could even not choose the right default options for the one project as it got overlapped by the other one. When setting up a (new?! custom?!) field there should be at least a big warning what could happen or just an error and info how to create a new field properly.

I'm fine with the renaming