I am trying to move issues from one next-gen project to another next-gen project, but the contents of all custom fields are lost out even if I select their "Retain" checkbox.
In both projects, I have defined exactly the same custom fields (same names, same type, same order). All them are of type "Paragraph" type within the "Description fields" category:
The fields above look identical for both projects (except for the crossed-out project name at the top, of course).
I am trying to move a Story as follows:
I then select the destination Project and Status, and come to the screen where I tell it to Retain the values of all custom fields:
However, in the next screen you can see that most of those fields are listed under both "Updated Fields" and "Removed Fields":
And after confirming the operation, the issue gets moved to the destination project and all the custom fields are empty:
What could be wrong? I've spent hours searching and trying different approaches to no avail.
I don’t know if things have changed since then, but after many days of research and trial-and-error, I was able to get an acceptable result back in May.
I think this includes all the steps I took:
I hope this helps!
I created a support case on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-569828
I recommend working with our Cloud support team to better understand the specifics of your problem here. I know that the next-gen projects handle custom fields differently than the classic projects do, but that said, I don't expect that your data would be lost during a move.
Perhaps we can update this Community post with more info once we resolve that support case.
It's not easy to say for me. I know your source project is a next-gen one, but it's not clear to me if the destination project is also next-gen, or perhaps a classic project. These two project types handle custom fields in different ways. For example when you create a custom field in a classic project you have the option to make this a global custom field. Which means that all projects can use that field. But next-gen projects don't default to do this. In fact all the custom fields you find in a next-gen project are isolated to that project. It can make it complex to correctly migrate data between these project types.
But I think it would be best to work with our Cloud support team in your case since they can request access to your Cloud site to see your data if you let them. This might help them to better understand the specifics and let us know if this is a misconfiguration, or bug/limitation of the move here.
Hi @Andy Heinzer - I'm having a similar issue. I'm trying to move issues from next-gen to classic to the same status, to reduce complexity. I understand that I will not be able to migrate my custom fields (my plan is to import them from a pre-migration export). However, description, comments, and email attachments are not included when I move the issue, even when I click retain description. What do I need to do to get the non-custom fields to move to the classic project?