Moving issues between projects displays render errors

[Scott McDonald]

Hello:

I'm attempting to move a number of issues from one project to another, however I'm receiving the following message on Step 3 of 4: Update Fields for Target Project 'Security-External ' - Issue Type 'Risk':

"CommentWhy/Rationale: Warning, the renderer type in the project you are moving to differs for this field, all the moved issues will be effected."

It's asking me for retain or enter a new value on fields that don't exist on either the project I'm moving from or the new project I'm wanting to move these issues to or if they do exist, they aren't required in the field configuration but they have a red asterisk next to them (see screenshot)

Thank you in advanced!

[Andy Heinzer]

The error in your screenshot though is a field requirement warning.   What has likely happened is that the destination project is using a different field configuration scheme.  This means that each field in that scheme could be setup to be required.  More details on how this is done in Specifying field behavior. 

In which case, you will have to have those issues with some value for those fields before they can be moved into that project.I believe you can get past this problem by either:

1. using the bulk issue editor in order to provide some values to each field for issues that have no value on that field
   
   OR
2. You can temporarily assign a different field configuration scheme to the destination project long enough to complete the import of this data.  

You might be able to complete the import by following the 2nd method, but you won't be able to edit the issues later on until you have provided values for each required field.   So in most cases, it's probably better to provide some value for these fields since the administrator of that project appears to have created those fields as required for a reason.