Renaming custom field options - Impact on filters

[Tobias]

Hello together, 

we have a customfield with all our customer service teams as its values. 

In cause of rebranding it is possible that some teams will be renamed our new ones will be created. For this situation I asked myself what the renaming of an custom field option would do to existing filters. 

Many teams have their team names referenced in a filter. Will this filter also be updated if the cf option will be renamed? 

I think disabling an option would still provide the option in issues which have the option set. 

Maybe you can report about your experiences with administering custom field options. 

Best 

Tobias 

[Benjamin]

HI @Tobias ,

In my experience, should be cautious in renaming options and the CF which will likely  cause the filters to break. If the filters break, then the dashboards and boards that uses them will not show up with the desire results.

It's better to plan ahead on change you will be doing. Identify which filters need to be updated.

-Ben

[mir_contact_stable_point_io]

Hi my name is mir I am the founder of Stable Point IO and the developer of the Impact Analysis for Jira app.

In Jira, renaming a custom field option does not break filters, as long as the option itself remains the same internal value (ID).

What happens when you rename an option

• The display value changes (what users see in UI, filters, dashboards, boards)
• The underlying option ID stays the same
• Therefore, existing JQL filters, boards, and dashboards continue to work correctly

So if you rename a team (e.g. for rebranding), your filters like:

"Customer Team" = "Old Name"

will automatically reflect the new name in the UI without breaking.

---

Important considerations

• If you delete an option instead of renaming it, Jira will ask you to migrate existing issues
• If you replace an option with a new one, then filters using the old value will need updating
• Dashboards and boards are safe as long as the option is not removed

---

Recommendation

Renaming is generally the safest approach for rebranding scenarios.

However, in large Jira environments, it’s still important to check where the field option is used before making changes, especially in:

• Filters (JQL)
• Automation rules
• Dashboards and boards
• Integrations

---

Plugin note (for impact visibility)

For better control and visibility before making changes like renaming or deleting options, you can use Impact Analysis for Jira.

It helps you:

• Identify where a custom field option is used (filters, workflows, automation, dashboards)
• Understand dependencies before making changes
• Reduce risk during large-scale configuration updates

More details here (for reference):
https://marketplace.atlassian.com/apps/4251492671/impact-analysis-for-jira?hosting=cloud&tab=overview

[Mohammed Shakhib]

This topic has been locked because the thread has become a bit dated. If you’d like to keep the conversation going or have any more questions, feel free to start a new topic. You can read more about necro posting (“raising threads from the dead”) in our  Community Guidelines .

Cheers!