Allow related issues to be started/due on the same date.
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.
Updated by Christopher Lörken over 13 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.
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
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.
Updated by Brian DeVries over 13 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.
Updated by red guv over 13 years 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.
It seems logical to include the precedes and follows in the sorting criteria for a gantt chart by default.
Updated by Siebe Joris Jochems about 10 years ago
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.
Updated by Marius BĂLTEANU over 5 years ago
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.