Redmine

Do you need more feedback?

So, I tried to track it down and here are some observations.

The r1592 has changed how custom fields are handled.
In /app/views/projects/_form.html.erb a line determining if custom field checkbox should be checked has been changed to use @project.all_issue_custom_fields. Today the code looks like this:

  <%= check_box_tag 'project[issue_custom_field_ids][]', custom_field.id, (@project.all_issue_custom_fields.include? custom_field),
        :disabled => (custom_field.is_for_all? ? "disabled" : nil),
        :id => nil %>

It seems that when project is copied the @project.all_issue_custom_fields returns nothing. The underlying SQL looks like this:

SELECT `custom_fields`.* FROM `custom_fields` 
WHERE `custom_fields`.`type` IN ('IssueCustomField') AND 
      (is_for_all = 1 OR id IN (SELECT DISTINCT cfp.custom_field_id FROM custom_fields_projects cfp WHERE cfp.project_id = NULL))  
ORDER BY `custom_fields`.`position` ASC

Notice that it checks for cfp.project_id = NULL, this seems to be wrong and suggests that at the time when @project.all_issue_custom_fields is called, the @project.id is not set.

The r11916 has changed the @project.all_issue_custom_fields to return a scope and include project id in WHERE causing the problem.