https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292017-09-27T16:52:08ZRedmineRedmine - Defect #26789: When copying an issue, the field assigned_to is not set as expectedhttps://www.redmine.org/issues/26789?journal_id=813252017-09-27T16:52:08ZToshi MARUYAMA
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/81325/diff?detail_id=64150">diff</a>)</li></ul> Redmine - Defect #26789: When copying an issue, the field assigned_to is not set as expectedhttps://www.redmine.org/issues/26789?journal_id=813272017-09-27T16:59:52ZToshi MARUYAMA
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Needs feedback</i></li></ul><p>I think it is expected behaviour if issue category has assignee.</p> Redmine - Defect #26789: When copying an issue, the field assigned_to is not set as expectedhttps://www.redmine.org/issues/26789?journal_id=813352017-09-28T08:40:57ZStéphane Briand SeaSideTech
<ul></ul><p>Toshi MARUYAMA wrote:</p>
<blockquote>
<p>I think it is expected behaviour if issue category has assignee.</p>
</blockquote>
<p>Thank you for your answer Toshi.<br />I confirm that the copied issue had its category property filled. And that category is assigned to someone.</p>
<p>So ok, now I understand why the <em>assigned to</em> property get automatically filled.</p>
<p>But, in my opinion, it is neither straightforward behaviour, nor what users expect.<br />The users explicitly clear the property <em>assigned to</em> when copying an issue, because they don't want that issue to be assigned yet.<br />And by magic, the property get filled automatically.</p>
<p>For me, the user's decision to let that property blank should be respected, and not overwritten.</p>
<p>Is it possible to change the behaviour of the Redmine Core this way? Or at least, add an option?</p>
<p>Many thanks</p>
<p>Stéphane</p> Redmine - Defect #26789: When copying an issue, the field assigned_to is not set as expectedhttps://www.redmine.org/issues/26789?journal_id=813432017-09-28T12:31:42ZMischa The Evil
<ul></ul><p>Stéphane Briand SeaSideTech wrote:</p>
<blockquote>
<p>[...] Or at least, add an option?</p>
</blockquote>
<p>You <em>could</em> change the behaviour by removing the assignee from the issue category altogether, although it is likely not exactly what you want.</p> Redmine - Defect #26789: When copying an issue, the field assigned_to is not set as expectedhttps://www.redmine.org/issues/26789?journal_id=813452017-09-28T12:50:42ZStéphane Briand SeaSideTech
<ul></ul><p>Mischa The Evil wrote:</p>
<blockquote>
<p>Stéphane Briand SeaSideTech wrote:</p>
<blockquote>
<p>[...] Or at least, add an option?</p>
</blockquote>
<p>You <em>could</em> change the behaviour by removing the assignee from the issue category altogether, although it is likely not exactly what you want.</p>
</blockquote>
<p>Ok, this is a solution.</p>
<p>For me, this tracker can be close.<br />Thank you.</p>
<p>Stéphane</p> Redmine - Defect #26789: When copying an issue, the field assigned_to is not set as expectedhttps://www.redmine.org/issues/26789?journal_id=813462017-09-28T14:17:21ZToshi MARUYAMA
<ul><li><strong>Status</strong> changed from <i>Needs feedback</i> to <i>Closed</i></li></ul><p>Thank you for your feedback.</p>