Redmine

Xiaochuan Lin wrote:

I also looked at the production.log file, and see the message,
"Project#copy_issues: issue #300 could not be copied: ..."

Could you past the actual full error message? That would be highly helpfull I guess.

Pasted in the following is a portion of the log information from the production.log file containing the actual full error message.

-----------------
...
Started POST "/redmine/projects/proj1/copy" for 127.0.0.1 at Wed Sep 12 10:41:51 +0800 2012
Processing by ProjectsController#copy as HTML
Parameters: {"utf8"=>"✓", "project"=>{"description"=>"", "tracker_ids"=>["1", "2", "3", ""], "parent_id"=>"", "identifier"=>"b", "name"=>"b", "issue_custom_field_ids"=>[""], "is_public"=>"1", "homepage"=>"", "enabled_module_names"=>["issue_tracking", "time_tracking", "news", "documents", "files", "wiki", "repository", "boards", "calendar", "gantt", ""]}, "only"=>["members", "versions", "issue_categories", "issues", "queries", "boards", "wiki", ""], "authenticity_token"=>"cfewI39ZPUH1m3cFHmx3Le3ITw9WZ2HJv/GJ4wi9oHs=", "commit"=>"Copy", "id"=>"proj1"}

Project#copy_issues: issue #1 could not be copied: customField1 can't be blankcustomField2 can't be blankcustomField3 can't be blank

Project#copy_issues: issue #2 could not be copied: customField1 can't be blankcustomField2 can't be blankcustomField3 can't be blank
Redirected to http://yfhdf-1/redmine/projects/b/settings
Completed 302 Found in 13279ms (ActiveRecord: 661.0ms)

...
-----------------

I just find that if I either set a default value or uncheck the 'Required' property of the custom field in the Administration page of Custom fields, the issues would be copied to the new project, however, the value of the custom field in the copied issue in the new project would be either the preset default value or blank accordingly.

Look forward your help, thanks much for your help and advice!

, i.e. the actual value of the custom field in the issues from the original project are not copied into the issues in the new project.

So, would this feature be included in a list of features to implement in the future version? thanks much for the help.

Jean-Philippe Lang wrote:

Xiaochuan Lin wrote:

So, would this feature be included in a list of features to implement in the future version? thanks much for the help.

No, you just can't copy these issues because they have invalid custom field values. After a custom field is made required, an issue with a blank value for this field can not be created.

Hi Jean,

I'm facing the same issue. Just that even if i set the issue required custom field to a valid value, it still failed to copy over. (in fact, it is Ok if copy just this issue. But if copy the whole project, this issue will not be copied as log report "issue could not be copied: xxxx can't be blank". But it's not blank and already set a valid value in the source issue.)

I am having the same issue. The custom field is not blank in the original issues but will not copy with the error that it can't be blank. I assume this is because there is no default value for the custom field. This is not resolved in any way.