https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292013-08-07T09:14:22ZRedmineRedmine - Defect #11481: Copying Projects (with Tickets) not workinghttps://www.redmine.org/issues/11481?journal_id=510662013-08-07T09:14:22ZEric Diaz
<ul></ul><p>Hi <br />same trouble in version 2.1.4<br />In my case, it seems that a mandatory custom fields fullfilled in sources tickets is the root cause.<br />If I put this custom field as no mandatory, tickets are well copied but all the custom fileds are set to null.</p>
<p>My opinion is that the first copy failed because all custom fields are set to null so that mandatory one's are in error.</p>
<p>Seems related to issue <a class="issue tracker-1 status-10 priority-4 priority-default" title="Defect: When I copy a project it does not copy the issues custom fields' values (Needs feedback)" href="https://www.redmine.org/issues/11315">#11315</a>, <a class="issue tracker-1 status-10 priority-4 priority-default" title="Defect: To copy project doesn't copy the issues' custom fields in version 2.2.3 (Needs feedback)" href="https://www.redmine.org/issues/13518">#13518</a> and <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: To copy project doesn't copy the issues' custom fields in version 2.3.0 (Closed)" href="https://www.redmine.org/issues/13540">#13540</a>.<br />As far as I m concerned, the solution porposed in <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: To copy project doesn't copy the issues' custom fields in version 2.3.0 (Closed)" href="https://www.redmine.org/issues/13540">#13540</a> doesn't work.</p>
<p>=======================================================<br />My environment :<br /> Redmine version 2.1.4.stable<br /> Ruby version 1.8.7 (x86_64-linux)<br /> Rails version 3.2.8<br /> Database adapter PostgreSQL 8.4.11</p>
<p>Regards</p> Redmine - Defect #11481: Copying Projects (with Tickets) not workinghttps://www.redmine.org/issues/11481?journal_id=510682013-08-07T09:26:18ZToshi MARUYAMA
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-10 priority-4 priority-default" href="/issues/11315">Defect #11315</a>: When I copy a project it does not copy the issues custom fields' values</i> added</li></ul> Redmine - Defect #11481: Copying Projects (with Tickets) not workinghttps://www.redmine.org/issues/11481?journal_id=510702013-08-07T09:26:36ZToshi MARUYAMA
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-10 priority-4 priority-default" href="/issues/13518">Defect #13518</a>: To copy project doesn't copy the issues' custom fields in version 2.2.3</i> added</li></ul> Redmine - Defect #11481: Copying Projects (with Tickets) not workinghttps://www.redmine.org/issues/11481?journal_id=510722013-08-07T09:26:57ZToshi MARUYAMA
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-4 priority-default closed" href="/issues/13540">Defect #13540</a>: To copy project doesn't copy the issues' custom fields in version 2.3.0</i> added</li></ul> Redmine - Defect #11481: Copying Projects (with Tickets) not workinghttps://www.redmine.org/issues/11481?journal_id=768632017-02-22T20:42:31ZMischa The Evil
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Needs feedback</i></li></ul><p>I just came around this issue again and checked whether this issue still persists on current trunk (at <a class="changeset" title="remove trailing white space from test/fixtures/workflows.yml" href="https://www.redmine.org/projects/redmine/repository/svn/revisions/16339">r16339</a>). AFAICS, this is fixed by <a class="changeset" title="Fixed that subtasks lose their custom fields when copying an issue to a different project (#22342)." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/15318">r15318</a> for <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: When copying issues to a different project, subtasks /w custom fields not copied over (Closed)" href="https://www.redmine.org/issues/22342">#22342</a>. I did some quick tests and wasn't able to reproduce the issue any longer.<br />Can this be confirmed by somebody?</p>