How To avoid historical tickets being updated due to Renaming Resolution value field?

[Victoria Aiksa Zapata]

Hello, 

I am new here and I could not find the accurate answer that I need for a problem we are facing at my company.

We've been asked to rename some values of the Resolution field but we need to avoid 

historical tickets to be updated due to the Renaming. Any suggestions? Thanks to all!!

Cheers!

Vicky

[Marc - Devoteam · Accepted solution]

Hi @Victoria Aiksa Zapata 

Welcome to the community.

The only option you have is to create new Resolutions and then bulk change the required issues.

Renaming options will mean that any issue using that option will be provided with the new name.

[Victoria Aiksa Zapata]

Hi Marc, thanks for the quick response! :)

Just to double-check, we want to have the renamed Resolution values applied to both new and historical tickets, but without impacting the resolution dates or any other metadata on the historical tickets. Is there any other way apart from your suggestion to ensure that this kind of change doesn’t accidentally alter historical data, apart from just updating the display name?

Thanks again for your help.

Cheers.

Vicky

[Marc - Devoteam]

Hi @Victoria Aiksa Zapata 

Filters looking for it will stop behaving, but that's about it. The name of a resolution is very much a label on an underlying object.

But you can't rename Jira system resolutions like the resolution "Done"