You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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?
Hi @Joe Pearson and welcome to the Community!
No. In the scenario you describe, Project A is not touched by your changes. You are introducing a new context for a new project.
The bug you refer to impacts existing issues that you are actively changing the context for. And that is not the case with the issues in Project A, so no worries.
Hope this helps!