How to avoid disruptions when adding new Resolution field values?

[Anthony Butler]

We have a team requesting to add new values to our Resolution field. Because they will be added companywide we are trying to understand the potential impact and avoid any disruptions with other projects including their filters, automations, etc.

Does anyone have experience with this and suggestions on how to best move forward?

[Gor Greyan · Accepted solution]

Hi @Anthony Butler

Welcome to the Atlassian Community!

In Jira, adding new resolution values is typically a low-risk change as long as you don’t rename or delete existing resolutions.

The main risk is logical gaps in filters, automations, reports, and scripts that explicitly reference old resolution values — those won’t automatically include the new ones and could lead to missing data or skipped workflow paths.

But overall, since the resolution list is global and additive, Jira itself won’t break. The real work is ensuring that downstream rules, JQL, dashboards, and automation logic are updated or flexible enough to handle the new values.

Also, you can check the Atlassian documentation on best practices on using the "Resolution" field.

https://support.atlassian.com/jira/kb/best-practices-on-using-the-resolution-field-in-jira-cloud/