https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292011-12-12T14:29:17ZRedmineRedmine - Defect #8936: rescheduling of an issue to an earlier date does not update issues that follow on this issuehttps://www.redmine.org/issues/8936?journal_id=346652011-12-12T14:29:17ZCassiano Monteiro
<ul></ul><p>This affects also version 1.1.1 .</p> Redmine - Defect #8936: rescheduling of an issue to an earlier date does not update issues that follow on this issuehttps://www.redmine.org/issues/8936?journal_id=349942011-12-22T16:19:10ZMischa The Evil
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Confirmed</i></li></ul><p>Confirmed on <a class="source" href="https://www.redmine.org/projects/redmine/repository/svn/revisions/7970/entry/trunk">source:/trunk@7970</a>.</p> Redmine - Defect #8936: rescheduling of an issue to an earlier date does not update issues that follow on this issuehttps://www.redmine.org/issues/8936?journal_id=475602013-03-27T03:06:54ZMischa The Evil
<ul><li><strong>Status</strong> changed from <i>Confirmed</i> to <i>Needs feedback</i></li></ul><p>Can't test it at the moment but I think this is implemented already via <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Precede-Follow relation should move following issues when rescheduling issue earlier (Closed)" href="https://www.redmine.org/issues/4590">#4590</a> in Redmine <a class="version" href="https://www.redmine.org/versions/56">2.2.0</a>.</p> Redmine - Defect #8936: rescheduling of an issue to an earlier date does not update issues that follow on this issuehttps://www.redmine.org/issues/8936?journal_id=897862019-02-03T18:47:34ZMarius BĂLTEANU
<ul><li><strong>Is duplicate of</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/4590">Feature #4590</a>: Precede-Follow relation should move following issues when rescheduling issue earlier</i> added</li></ul> Redmine - Defect #8936: rescheduling of an issue to an earlier date does not update issues that follow on this issuehttps://www.redmine.org/issues/8936?journal_id=897882019-02-03T18:48:10ZMarius BĂLTEANU
<ul><li><strong>Status</strong> changed from <i>Needs feedback</i> to <i>Closed</i></li><li><strong>Resolution</strong> set to <i>Duplicate</i></li></ul> Redmine - Defect #8936: rescheduling of an issue to an earlier date does not update issues that follow on this issuehttps://www.redmine.org/issues/8936?journal_id=897892019-02-03T18:48:47ZMarius BĂLTEANU
<ul></ul><p>Mischa The Evil wrote:</p>
<blockquote>
<p>Can't test it at the moment but I think this is implemented already via <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Precede-Follow relation should move following issues when rescheduling issue earlier (Closed)" href="https://www.redmine.org/issues/4590">#4590</a> in Redmine <a class="version" href="https://www.redmine.org/versions/56">2.2.0</a>.</p>
</blockquote>
<p>Indeed, the issue was fixed in <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Precede-Follow relation should move following issues when rescheduling issue earlier (Closed)" href="https://www.redmine.org/issues/4590">#4590</a>.</p>