Defect #11549

Start date of 2nd issue does not follow if the first issue end date moves up

Added by john zhel over 9 years ago. Updated over 9 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Resolution:Duplicate Affected version:2.0.3


I have 2 issues.

I set Issue 002 follows Issue 001. Issue 001's end date is Sept 1st.

If I change the end date of Issue 001 to 5 days later (to Sept 6th), I see Issue 002's start and end date aslo move forward (later) 5 days, which is good.

Here is the problem: if I move the end date of Issue 001 to 5 days earlier (to August 25th), the Start date and end date of Issue 002 does not move accordingly, instead, they just stay where they were - no changes. Why is that? How to fix it?


Related issues

Duplicates Redmine - Defect #8936: rescheduling of an issue to an earlier date does not upda... Closed 2011-07-28


#1 Updated by john zhel over 9 years ago

Just to clarify: "I have 2 issues." in my previous post means I created 2 new issues in my Redmine to test out the related issue feature (one follows the other).

#2 Updated by john zhel over 9 years ago

Found a solution here:

where it says "•Fixed rescheduling of related tasks if due date of dependent task changed to an earlier date."

Just wondering, if there is a special reason the core makes it this way? Any idea?

#3 Updated by Jean-Philippe Lang over 9 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

No particular reason, it's just not implemented.

Also available in: Atom PDF