Adding grouping values without messing up historical stats

Karin Kennergren April 28, 2024

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?

1 answer

1 accepted

1 vote
Answer accepted
Victor Law
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 29, 2024

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 April 29, 2024

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
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 29, 2024

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

Like Karin Kennergren likes this
Karin Kennergren April 29, 2024

Thank you for confirming!

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events