Defect #4154

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

Added by Michael Aye over 8 years ago. Updated 3 months ago.

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

0%

Category:Issues
Target version:-
Resolution:Fixed 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


Related issues

Related to Redmine - Patch #28649: Log automatic rescheduling of following issues to journal Closed

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 almost 3 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 about 1 year ago

+1

#6 Updated by Go MAEDA 4 months ago

  • Target version set to Candidate for next major release

#7 Updated by Kevin Fischer 4 months 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?

#8 Updated by Go MAEDA 3 months ago

  • Related to Patch #28649: Log automatic rescheduling of following issues to journal added

#9 Updated by Go MAEDA 3 months 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.

Also available in: Atom PDF