How do I retain custom field values when moving issues from new-gen project to a classic project?

Question

My use case: I am moving all my issues from a new-gen project to a classic project.

I have 3 custom fields that I created in the New-Gen project.

I created 3 global custom fields in Classic.

When I go to move all my issues using the bulk-move, no where am I prompted to map the custom fields from new-gen to classic. I am essentially losing all of the data that I have in those fields.

I know I can export/import, but should I not be prompted to map those custom fields while doing a bulk move?

Jamie Schwartz · Answer

I agree this should be future enhancement because when working with Jira Issues you want to keep the old URLs people have redirecting to the new issue when it's moved. Exporting and importing via csv doesn't seem to do that. Ideally you'd get the same screen you get when doing an csv import when moving issues from Teams to Company or Company to Company projects because not every project is exactly the same and should be a change to map the values. This is especially frustrating with service projects because we have both company and team projects and issues need to move all the time.

Diego Alzugaray_okn69c · Answer

Ultimately, I just did a CSV export/Import into the new project. I think the issue is custom fields don't necessarily act the same in Next-Gen vs Classic.

The bulk mover is an excellent tool, so if custom fields aren't available to move between themes, then there must be a good reason for it. Maybe it can go in as a future enhancement?

John Funk · Answer

I was thinking that maybe you could do a bulk change, but since they are unique values, that wouldn't work.

The other option might be using the Scheduled trigger in Automation For Jira.