Vote #76287
完了Issue Estimated Time not updated on tracker change
0%
説明
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.
journals
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.
--------------------------------------------------------------------------------
I have put this simple patch to the method mentioned above.
This seems to resolve the problem so far
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
See the latest file
--------------------------------------------------------------------------------
Fixed in r14180, thanks for pointing this out.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------