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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello,
I have a scenario here and would like to understand.
Scenario:
I have few custom fields which are part of Global Context. These fields are already being used and have many existing issues with the values. Now if I try to migrate these custom fields from Global Context to specific Project Context, does Jira(server) take care (copy values) of all the existing issues data in the new Project Context? Or the data gets erased and I need to get the list of issues through a script and update the values?
I have gone through this link and I didn't get clarity.
https://confluence.atlassian.com/adminjiraserver/custom-fields-with-global-contexts-956713282.html
Thanks!
Kumar
Hi @KL Kumar ,
As stated in this KB, "there is no risk of data loss" : changing the context will not erase the values. You can safely switch. :)
Thanks @Antoine Berry .
But when I try to implement such case, I see only for few custom field types, there is no data loss for existing issues. For example, there's no data loss for Select List, Cascading Select List, Radio buttons, etc. But there's data loss specifically for Checkbox and Multiple Select List types. So when I migrate from Global context to Project context, the data for these two custom field types is erased and not visible for the existing issues.
Thanks,
Kumar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You should check if those fields share the same default and project configurations. If those are different (meaning they do not have the same options available), data will be erased.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.