Project

General

Profile

Actions

Defect #8936

closed

rescheduling of an issue to an earlier date does not update issues that follow on this issue

Added by Anonymous over 13 years ago. Updated almost 6 years ago.

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

0%

Estimated time:
Resolution:
Duplicate
Affected version:

Description

Issue B follows on issue A, (B can only start when A is done). When the due date for issue A is set to an earlier date, the start date of issue B does not reschedule.

The test for rescheduling does not test this scenario:

 def test_rescheduling_an_issue_should_reschedule_following_issue
    issue1 = Issue.create!(:project_id => 1, :tracker_id => 1, :author_id => 1, :status_id => 1, :subject => '-', :start_date => Date.today, :due_date => Date.today + 2)
    issue2 = Issue.create!(:project_id => 1, :tracker_id => 1, :author_id => 1, :status_id => 1, :subject => '-', :start_date => Date.today, :due_date => Date.today + 2)
    IssueRelation.create!(:issue_from => issue1, :issue_to => issue2, :relation_type => IssueRelation::TYPE_PRECEDES)
    assert_equal issue1.due_date + 1, issue2.reload.start_date

    issue1.due_date = Date.today + 5
    issue1.save!
    assert_equal issue1.due_date + 1, issue2.reload.start_date
  end

Extending the test to include scheduling the other way (back) too:

 def test_rescheduling_an_issue_should_reschedule_following_issue
    issue1 = Issue.create!(:project_id => 1, :tracker_id => 1, :author_id => 1, :status_id => 1, :subject => '-', :start_date => Date.today, :due_date => Date.today + 2)
    issue2 = Issue.create!(:project_id => 1, :tracker_id => 1, :author_id => 1, :status_id => 1, :subject => '-', :start_date => Date.today, :due_date => Date.today + 2)
    IssueRelation.create!(:issue_from => issue1, :issue_to => issue2, :relation_type => IssueRelation::TYPE_PRECEDES)
    assert_equal issue1.due_date + 1, issue2.reload.start_date

    issue1.due_date = Date.today + 5
    issue1.save!
    assert_equal issue1.due_date + 1, issue2.reload.start_date

    issue1.due_date = Date.today + 2
    issue1.save!
    assert_equal issue1.due_date + 1, issue2.reload.start_date
  end


Related issues

Has duplicate Redmine - Defect #11549: Start date of 2nd issue does not follow if the first issue end date moves upClosed

Actions
Is duplicate of Redmine - Feature #4590: Precede-Follow relation should move following issues when rescheduling issue earlierClosedJean-Philippe Lang2010-01-15

Actions
Actions #1

Updated by Cassiano Monteiro about 13 years ago

This affects also version 1.1.1 .

Actions #2

Updated by Mischa The Evil almost 13 years ago

  • Status changed from New to Confirmed

Confirmed on source:/trunk@7970.

Actions #3

Updated by Mischa The Evil over 11 years ago

  • Status changed from Confirmed to Needs feedback

Can't test it at the moment but I think this is implemented already via #4590 in Redmine 2.2.0.

Actions #4

Updated by Marius BĂLTEANU almost 6 years ago

  • Is duplicate of Feature #4590: Precede-Follow relation should move following issues when rescheduling issue earlier added
Actions #5

Updated by Marius BĂLTEANU almost 6 years ago

  • Status changed from Needs feedback to Closed
  • Resolution set to Duplicate
Actions #6

Updated by Marius BĂLTEANU almost 6 years ago

Mischa The Evil wrote:

Can't test it at the moment but I think this is implemented already via #4590 in Redmine 2.2.0.

Indeed, the issue was fixed in #4590.

Actions

Also available in: Atom PDF