Time spent in merge requests should be reflected as progress toward a milestone.
Problem to solve
Time tracking against Milestones appears to only capture Issue spend. When a developer marks time spent in merge requests this is not captured.
Further details
The only way we can mark burndown or milestone progress useful is to force developers to go back to the issue to spend time rather than doing so in the merge request they are working on.
Proposal
Either include time spent on merge requests in the total time on the right hand side or show a separate total for MR spent time.
What does success look like, and how can we measure that?
Time spent in merge requests should be reflected as progress toward a milestone.