Is this the correct Jira approach to replace a field with a new one while retaining historical data

[Mahanth Prudhvi P]

For one function we are using a field "ABC" and now we wanted to replace that with another field & name "QWERTY" for the same function. We dont want to loose the old data from "ABC" field even for the that are already closed. So I am thinking to add those values to the new field "QWERTY" and then remove the old field and delete it. By following this there will be an log in the ticket history even for the ones that are closed.
In general Jira principle is this correct approach?

Note: We have a status property that does not allow to make any more changes to tickets once they are closed. I will have remove it and do the activity and then add again.

[Arkadiusz Wroblewski]

Hello @Mahanth Prudhvi P 

For me your approach seems legit.

You want to at least be able to reproduce that. You never know when you will need some data and then regret you don't have it.

Best,

Arek 🤠