Adding grouping values without messing up historical stats

[Karin Kennergren]

Hi community!

We have a custom field with options representing different cost centers for our clients, but we need to group them by company. For instance, 'Company A UK1' and 'Company A Sweden' should both be under 'Company A.' How can we achieve this without losing history/values, considering the field wasn't originally set up as cascading?


Any tips on tackling this issue?

[Victor Law · Accepted solution]

Hi @Karin Kennergren

As long as the custom field is not deleted, the values and history will remain in the Jira Cloud environment.

You may archive the values no longer used to prevent the user from selecting them. Achieving a field value will NOT remove the history, and the Jira issue will remain searchable.

Alternatively, you may consider bulk updating the new Cascading field based on the value in the existing custom field.

Thank you.

[Karin Kennergren]

Thanks much, confirming my assumptions. I believe cascading field is the way forward since it "force" the one that is updating with new options to structure the cost centers. 

[John Funk]

Yes, you should populate the cascading field with the values of the existing field. Then you can delete the old field. 

[Karin Kennergren]

Thank you for confirming!