Log automatic rescheduling of following issues to journal
|Assignee:||Jean-Philippe Lang||% Done:|
The bug described in #4154 seems to be already fixed.
The attached patch fixes a related bug, because of which updates to the due date of a preceding issue were not reflected in the following issue's history.
#2 Updated by Go MAEDA about 2 years ago
- Target version set to 3.3.8
I confirmed the problem and the patch looks good to me, setting target version to 3.3.8.
When you add a "Follows" relation to an issue and if the start date of the following issue is sooner than the due date of the preceding issue, start date and due date of the following issue will be automatically updated and those updates are logged to the journal. It is the expected behavior.
However, if the dates of the following issue are automatically updated by editing the due date of preceding issue, nothing is logged to the journal. This case should also be logged to the journal, as Kevin Fischer pointed out.
#5 Updated by Mischa The Evil about 2 years ago
- issue relations: #27644, which, I think, would be fixed by the patch proposed in this issue (along with r13534 as you have mentioned yourself in issue #4154#note-9)
- parent-child relations: the subject of #6687 and #5875
- default custom field values: a side-effect of the implementation of #21074, reported in #25726#note-4