At the moment when you moved a feature to shipped then the time recording changes to be the same as the estimate. So for example if I estimated 3 days, actually only took and recorded 2 days when I ship the feature the time taken changes to 3 days automatically even though I never did that additional day. This means that once the product has shipped I have no way of comparing the estimated vs actual time a feature took, which is a very valuable information in proving estimating and planning.
I appreciate that for some they may want the time logged to just reflect the estimate if they don't wish to log time taken, but at the point that today you move it to shipped you could ask do you want the time taken updated to match the estimate yes or no. to keep it simple but optional.
|Release time frame|
Feature logging and estimates currently are kept as separate values when shipping.
When logging time, there is the option to indicate whether the Remaining estimate should be updated automatically, or whether it should be set to a specific number (such as 0, in the case where all work has been completed).
By specifying the remaining estimate, this will prevent the remaining estimate from automatically updating to equal the original estimate, when shipping.
This will allow you to compare logged effort vs. the original estimate.