Defect #4154
closed
Automatic rescheduling by precedes issue-relation should be added to the journal
0%
Description
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.
Files
Related issues
Updated by Anonymous
Updated by Mischa The Evil over 13 years ago
- Subject changed from Automatic rescheduling should be listed in history to Automatic rescheduling by precedes issue-relation should be added to the journal
Updated by Sebastian Paluch over 8 years ago
+100
Additionally, there is no email notification that the dates for task A has changed.
Updated by 
Updated by 
Updated by Go MAEDA about 6 years ago
- Target version set to Candidate for next major release
Updated by Kevin Fischer about 6 years ago
- File After setting relation - Task A.png After setting relation - Task A.png added
- File After setting relation - Task B.png After setting relation - Task B.png added
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.
Task B:
Task A:
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?
Updated by Go MAEDA almost 6 years ago
- Related to Patch #28649: Log automatic rescheduling of following issues to journal added
Updated by Go MAEDA almost 6 years ago
- Status changed from New to Closed
- Target version deleted (
Candidate for next major release) - Resolution set to Fixed
Kevin Fischer wrote:
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.
I confirmed that the problem described in this issue is already fixed by r13534 (Redmine 3.0.0). Thank you for pointing it out and isolating the similar problem you have reported as #28649.