What is your methodology for transitioning from one field type to another in an active project?

[Penn]

I have field within a very active project that asks for a number. For this example it is "How many carrots does your carrot patch grow?" This field asks for a specific number. The data own for the results of the value for this field find that this is causing issues and instead is now asking for a range. Now they would like to see a radio button like:

"How many carrots does your carrot patch grow?"
Small: 0< 10
Medium: 11 < 100
Large: 100+

Technically this is a simple transition, I just rip out the old field from the screen and add the new field...but is this the right method? Should I hide the old field because previous Jira issues contain a value? Should I retroactively go back and change these values (hundreds of issues)?

[Trudy Claspill · Accepted solution]

Are there reports, filters, dashboards, or workflow conditions/validators/post-functions that depend on that field? Are those being adjusted to no longer be dependent on the original field?

If the old field is no longer needed, and you are absolutely sure about that, what I would choose to do is:

1. Copy the data for that field to a Comment. Use Automation for Jira to do this. I record the value of a field being removed just in case there is some need in the future to know what that value was.

2. Create the new field.

3. Use Automation for Jira to look at all the old issues that have a value in the old field, evaluate that value, and set the new field for each of those issues.

4. Remove the old field.

[Penn]

Interesting approach! I like it! Thank you @Trudy Claspill !