Hey Team -
The above bug notes that when adding a new context to an existing custom field, historical values may be wiped (reset to null).
Does this apply in the following situation:
Project A uses custom_field_1 with values 7,8,9,0, and uses the default / global context.
Project B is being created, and wants a new context for custom_field_1 to contain values 6,7,8,9.
If I create a new context for custom_field_1 that applies only to Project B with my new set of values, will the issues in Project A which rely on the default/global context fall victim to JRACLOUD-62455?
Thanks Team!