Feature #5655

Allow related issues to be started/due on the same date.

Added by Dan Olsen almost 2 years ago. Updated over 1 year ago.

Status:New Start date:2010-06-08
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:-
Target version:-
Resolution:

Description

When I have issue A and issue B, and I assign issue B to follow issue A I want to still be able to schedule the start date for both A and B on the same day.

Currently if I schedule issue A and issue B to start on the same day, than I say issue B follows issue A, issue B's start date is changed to the next day after issue A's due date. Issue A may only take an hour which means issue A and issue B could technically start on the same day.

Instead of moving the B date out a day after the due date of A, set the start date of B to the due date of A and then let me change the start date of B if it needs to be the next day.

seq_issues_start_end_same_day.patch - Patch of the fix in comment 1 against r3940 (534 Bytes) Magnifier Brian DeVries, 2010-08-17 10:23

Related issues

duplicated by Feature #6127: Preceeded by / followed by - Same day Closed 2010-08-13

History

#1 Updated by Christopher Lörken almost 2 years ago

I've encountered the same issue.

I have fixed this for me like this:
In version 0.9.4 open your app/models/issue_relation.rb file and go to line 79.

Replace 

  def successor_soonest_start
    return nil unless (TYPE_PRECEDES == self.relation_type) && (issue_from.start_date || issue_from.due_date)
    (issue_from.due_date || issue_from.start_date) + 1 + delay
  end

with

  def successor_soonest_start
    return nil unless (TYPE_PRECEDES == self.relation_type) && (issue_from.start_date || issue_from.due_date)
    (issue_from.due_date || issue_from.start_date) + delay
  end

in other words: remove the "+ 1" from line 79.
Restart your web server and you can choose the same start and enddates for following tasks.

#2 Updated by Brian DeVries almost 2 years ago

As a side note, at least in r3940, this is now on line 94. I've included a patch with this change.

As a question, what would be the general requirements for this feature to be included in Redmine proper? Depending on the complexity, I figure this might be a good introduction to Redmine hacking for me.

#3 Updated by red guv over 1 year ago

Great thanks, Is this being placed into the trunk?

I have noticed that the fix works but gantt charts sort by issue id when tasks are on the start on the same day.
The sort should take into account precedes and follows relationships.

I see the following issue but no action on it.
http://www.redmine.org/issues/3436

It seems logical to include the precedes and follows in the sorting criteria for a gantt chart by default.

#4 Updated by Gabriel Mazetto over 1 year ago

There is a patch to this issue, why it's not merged in the trunk yet?

Also available in: Atom PDF