Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Copying values for existing issues while migrating from Global Context to Project Context


I have a scenario here and would like to understand. 


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.





1 answer

1 accepted

0 votes
Answer accepted
Antoine Berry Community Leader Jan 20, 2020

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.



Antoine Berry Community Leader Jan 21, 2020

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.

Like Antoine Berry likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

167 views 6 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you