Project

General

Profile

Actions

Defect #11549

closed

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

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

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Duplicate
Affected version:

Description

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?

Thanks!


Related issues

Is duplicate of Redmine - Defect #8936: rescheduling of an issue to an earlier date does not update issues that follow on this issueClosed2011-07-28

Actions
Actions #1

Updated by john zhel over 12 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).

Actions #2

Updated by john zhel over 12 years ago

Found a solution here:
http://www.redmine.org/plugins/redmine_better_gantt_chart

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?

Actions #3

Updated by Jean-Philippe Lang over 12 years ago

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

No particular reason, it's just not implemented.

Actions

Also available in: Atom PDF