Defect #19606: Issue Estimated Time not updated on tracker change - Redmine

Actions

Copy link

Defect #19606

closed

Issue Estimated Time not updated on tracker change

Added by Stephane Evr over 9 years ago. Updated over 9 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Jean-Philippe Lang

Category:

Issues

Target version:

3.0.2

Start date:

Due date:

% Done:

Estimated time:

Resolution:

Fixed

Affected version:

3.0.1

Description

The problem occurs when the issue tracker is changed to another which does not have the estimated time field activated:

- Create a main issue with a tracker which has the "Estimated time" field
- Create a subtask with a tracker which has also the the "Estimated time" field and set it to X hours
- Change the tracker of this subtask to another which does not have the the "Estimated time" field activated
- Go to the parent task

Result: Estimated time on the parent task is still X hours

From my searches, I can see that the issue estimated time is not changed in DB. It won't change to null, but remain to X hours.

Files

Download all files

issue_tracker_estimated_time.diff (508 Bytes) issue_tracker_estimated_time.diff	issue.rb patch	Stephane Evr, 2015-04-14 11:34
issue_tracker_estimated_time.diff (471 Bytes) issue_tracker_estimated_time.diff	issue.rb patch	Stephane Evr, 2015-04-14 11:58

Actions

Copy link

Updated by Stephane Evr over 9 years ago

I had a deeper look into the code, I think that the method to patch is
tracker=(tracker) in app/models/tracker.rb where in case the new tracker does not have the Estimated Time field activated, we nullify the estimated time of the issue.

Actions

Copy link