Mapping issue fields when moving issues from one project to another

Rim Ben Rejab

Hi guys,

the "move issues" from one project to another seems complicated especially regarding fields mapping.

In this article (Moving an issue - Jira Software Server 8.3 - Atlassian Documentation), it is stated that "  If you have defined required custom fields for your issue that do not exist in your target project, you must set values for them". 

What values?? the fields might not even exist in the new project's issue types.

Also, when I checked the retain values from my estimation points and I migrated the issues, Poof! Gone. No estimation point was kept as it was in the source project.

and what does it mean here by saying " Other incompatible fields will also appear empty, even if users choose to retain their values. "

why would I have the option to retain them then?

 

Long story short, can anyone just tell me what is kept and what is left in issue fields from the source project? because I couldn't really find any good document on this matter.

 

Thank you so much

Nic Brough -Adaptavist-

Hi Rim,

There's a lot here

 

> " If you have defined required custom fields for your issue that do not exist in your target project, you must set values for them".

> What values?? the fields might not even exist in the new project's issue types.

You must have added the fields to the new project - you can't make them mandatory if they are not there!

>Also, when I checked the retain values from my estimation points and I migrated the issues, Poof! Gone. No estimation point was kept as it was in the source project.

That suggests that the target project does not have field you are trying to migrate.

>and what does it mean here by saying " Other incompatible fields will also appear empty, even if users choose to retain their values. "

If you have a field in the source project which is of one type, and a field with the same name in the target, but of a different type, then you will lose the data.  You can not stuff text data into a date/time field, for example.  Also, if you have list fields, you need to make sure you map the values, or have options on the list that match.