Actions
Feature #4590
closed
Precede-Follow relation should move following issues when rescheduling issue earlier
Start date:
2010-01-15
Due date:
% Done:
0%
Estimated time:
Resolution:
Fixed
Description
Hi,
Suppose Task1 precedes Task2...and when I postpone Task1, then Task2's start date gets postponed as well. However, when Task1 gets moved earlier, Task2's start date remains as-is; effectively detaching the precede-follow relationship. Is it possible to implement so that precede-follow relationship remains when tasks get moved in either direction?
Related issues
Updated by tengel liu over 14 years ago
This can be done by apply following code
--- 1/app/model/issue.rb 2010-04-29 13:52:50.000000000 +0800
+++ 2/app/model/issue.rb 2010-04-29 14:32:20.000000000 +0800
@@ -446,7 +446,7 @@
def reschedule_after(date)
return if date.nil?
if leaf?
- if start_date.nil? || start_date < date
+ if start_date.nil? || start_date != date
self.start_date, self.due_date = date, date + duration
save
end
Updated by
Updated by Aurélien Appéré over 13 years ago
Still having the same problem in version 1.2.1 stable.
Updated by Jean-Philippe Lang about 12 years ago
- Subject changed from Precede-Follow relation moves backward to Precede-Follow relation should move following issues when rescheduling issue earlier
- Status changed from New to Closed
- Assignee set to Jean-Philippe Lang
- Target version set to 2.2.0
- Resolution set to Fixed
Implemented in r10878.
Updated by Marius BĂLTEANU almost 6 years ago
- Has duplicate Defect #8936: rescheduling of an issue to an earlier date does not update issues that follow on this issue added
Actions