Defect #4154

Automatic rescheduling by precedes issue-relation should be added to the journal

Added by Michael Aye over 8 years ago. Updated 22 days ago.

Status:NewStart date:2009-11-02
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:Candidate for next major release
Resolution: Affected version:0.8.5

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.

After setting relation - Task B.png (29.2 KB) Kevin Fischer, 2018-04-04 06:12

After setting relation - Task A.png (55 KB) Kevin Fischer, 2018-04-04 06:12

History

#1 Updated by Anonymous over 8 years ago

+1

#2 Updated by Mischa The Evil over 7 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

#3 Updated by Sebastian Paluch over 2 years ago

+100

Additionally, there is no email notification that the dates for task A has changed.

#4 Updated by Kamil Franckiewicz over 2 years ago

+1

#5 Updated by Mitsuyoshi Kawabata 10 months ago

+1

#6 Updated by Go MAEDA 24 days ago

  • Target version set to Candidate for next major release

#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.

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?

Also available in: Atom PDF