https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292013-01-28T08:14:10ZRedmineRedmine - Defect #12968: Subtasks don't resepect following/precedeshttps://www.redmine.org/issues/12968?journal_id=450792013-01-28T08:14:10ZDaniel Felix
<ul></ul><p>I encountered some error which seems to relates to the same problem.</p>
<p>For example:<br />- Task A<br />-- Task A1<br />-- Task A2<br />- Task B<br />-- Task B1<br />-- Task B2<br />- Task C</p>
<p>Task C follows A, Task B1 follows C, Task B2 follows B1</p>
<p>If I set some follow or precede on subtask, where the parent task already has precedes or follows relations, these relations will be automatically removed without any warning or errormessage. I encountered this several times.</p> Redmine - Defect #12968: Subtasks don't resepect following/precedeshttps://www.redmine.org/issues/12968?journal_id=467422013-03-17T09:28:47ZDaniel Felix
<ul><li><strong>Target version</strong> set to <i>2.3.0</i></li></ul><p>This should be rechecked before 2.3 release.</p>
<p>Can anyone still confirm this?</p> Redmine - Defect #12968: Subtasks don't resepect following/precedeshttps://www.redmine.org/issues/12968?journal_id=467452013-03-17T10:54:06ZMoe H
<ul></ul><p>I have rewritten the all_dependent_issues function in the issue model, which should eliminate the problem with circular dependency. But i'm not sure how to contribute it.</p> Redmine - Defect #12968: Subtasks don't resepect following/precedeshttps://www.redmine.org/issues/12968?journal_id=467472013-03-17T11:39:52ZDaniel Felix
<ul></ul><p>Hi,</p>
<p>Maybe your firm with tortoise. Just generate a diff with your changes.</p>
<p>If not, just upload a file with the corresponding function.</p>
<p>Maybe toshi or jean-Philippe can review this and apply the changes to the core.</p>
<p>This way it could be fixed before Redmine 2.3 will be released.</p> Redmine - Defect #12968: Subtasks don't resepect following/precedeshttps://www.redmine.org/issues/12968?journal_id=467692013-03-17T15:23:23ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li><li><strong>Assignee</strong> set to <i>Jean-Philippe Lang</i></li><li><strong>Resolution</strong> set to <i>Fixed</i></li></ul><p>Moe H wrote:</p>
<blockquote>
<p>In the current development version, there is a bug <br />Imagine following scenario:<br />There are 2 tasks: "Issue1" and "Issue2", and "Issue2" follows "Issue 1" by x days. This works fine. But if I add an subtask to "Issue2" the startdate is not correctly set to Issue1.enddate + x, instead it is possible to set any date you want, without respecting the Issue Relation.</p>
</blockquote>
<p>Fixed in <a class="changeset" title="Fixed: subtasks don't resepect following/precedes relations on creation (#12968)." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/11640">r11640</a>.</p>
<blockquote>
<p>Furthermore, it is possible to set a relation so the subtask precedes "Issue 1", which creates a circular dependency.</p>
</blockquote>
<p>Fixed as part of <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: Circular loop when using relations and subtasks (Closed)" href="https://www.redmine.org/issues/8794">#8794</a>.</p>
<p>Thanks for pointing this out.</p> Redmine - Defect #12968: Subtasks don't resepect following/precedeshttps://www.redmine.org/issues/12968?journal_id=470772013-03-19T18:37:46ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul><p>Merged.</p>