Redmine

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.

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.

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

I have the same problem. I use the gantt chart a lot and I love the arrows between issues. When working with small issues (2 hours) a lot of those will start/end on the same day.

Another workaround for this issue is to specify a delay of -1 days when linking the issues.

8 years later, is there any update on this?
Using a delay of -1 certainly works but it's incredibly confusing to anyone who doesn't know why it was necessary to do so.

Sebastian C wrote:

8 years later, is there any update on this?
Using a delay of -1 certainly works but it's incredibly confusing to anyone who doesn't know why it was necessary to do so.

There were some discussions about this on #3195. I'll close this issue as duplicated.