Automatic rescheduling by precedes issue-relation should be added to the journal
|Target version:||Candidate for next major release|
If the scheduled dates of task A are automatically changed by setting a 'precedes' relationship inside task B, this really is required to be listed in the history of task A, otherwise the information, to which dates task A was set before, is lost.
#7 Updated by Kevin Fischer 22 days ago
Assuming the situation described in this issue and using the latest revision (r17255):
Task B --precedes--> Task A
When setting a precedes relationship inside task B, the rescheduling of Task A that occurs, is listed properly in the Task A's history.
So unless I'm misunderstanding this issue's description, this issue is already resolved.
But if you change Task B's due date (after the relation is established), the rescheduling of Task A in this case is not listed in Task A's history....
Is there an issue about that particular part of the bug? Or should the description of this issue be adapted to be more specific about the bug?