Do not include closed issues in milestone "Time remaining"
Description
When visiting the milestones page (/{user}/{project}/milestones/{id}
), you can view the time tracking status in the sidebar.
You can see total time spent on all issues so far, total time estimated on all issues, and, on hover, estimated time remaining.
Problem: Estimated time remaining includes issues that have already been closed.
Why is this a problem? Estimated time remaining can become significantly out-of-sync with your own expected estimates. If you estimate an issue to take 15m, but resolve it in 5m and close the issue, it should be pretty clear that you don't expect to spend further time on the issue. However, the milestones page still include the closed issue in the estimated time remaining, so it displays an estimate higher than you expect.
As more issues are closed and their spent time differs from their estimates, the estimated time remaining metric becomes progressively less accurate unless you /remove_estimate
on each issue as you close it. But this causes loss of information which may be valuable later on.
Tl;dr - why are you including closed issues in milestone estimated time remaining? I do not believe this is an expected behaviour and it compromises the usability of the milestones page. If an issue is closed, I do not expect to spend further time on it, and I expect the milestones page to only show me the estimated time required to complete the outstanding issues.
Proposal
Do not include closed issues in the Milestone page time tracking "estimated time remaining."