Custom fields not retaining value on bulk more

Edgar Oregel_1g2cuw

I'm trying to bulk move issues from one project to another for a customer, but the custom fields aren't retaining their values. I triple checked that the schemes are all the same between the two projects, the fields exist in the create screen, field configurations, and that they have all the same field options as they do in the original project (since they're dropdowns), but when i go to do a bulk move, check the "Retain Value" checkbox, and arrive at the confirmation page, the details state that the new value of the 2 custom fields are empty. 

I already moved one issue over to the new project thinking that the custom field's values will be updated in the other project to their original values after the move, but they didn't. The custom fields both were changed to empty values. 

Edgar Oregel_1g2cuw

I figured it out!! Well, you did, @Andy Heinzer. You were right. Since the drop-down fields use unique IDs for the drop-down option values, if i make a new configuration for the same custom field, the values are now going to have new IDs, and therefore cannot retain the value since it doesn't exist in terms of the ID in the new project configuration. 

The solution was to just add the new project to the old project configuration scheme so that it can use the same field value IDs in the background. As i said, when i did this, the custom field no longer appeared in the fields list right before confirming the move, however, I tested it, and the value is retained. I assume that since the field is using the same configuration scheme and therefore the same value IDs, JIRA just decides it doesn't need to show you the field nor the value just like it does with Summary, Issue Type, Description, etc. - those fields aren't in the list either, but yet they are moved.