Report time spent per user in a particular project or milestone
Description
-
The burndown chart is against completed tasks. Would be great to have it against time spent on each task.
-
Look at the time spent by a user on a particular milestone. What did "team-member-1" spent their time on this particular milestone/project? I imagine we could get some of it from cycle analytics, but the reporting seems task-centric rather than user-centric.
-
How much time is allocated to each project member for the milestone? How much time has the project member spent doing their tasks?
Proposal
-
Add the ability to view burndown chart progress based on the time spent/estimate for a particular milestone. This way we can see progress when a task is still partially completed
-
Report on how much work each user is allocated to based on the time estimates for the issues assigned to them. And how much progress they made for the milestone/project (i.e. the total time spent of the total hours allocated to them).
-
In the issues board, try to give a visual clue of the completeness of each particular task without having to open each one of them (e.g. a pie chart, progress bar, % number, etc).
Links / references
Documentation blurb
Overview
What is it?
- Reporting features that are frequently used by project managers. Instead of looking up every task and try to work the numbers/overall progress of a project manually, the product could help them.
Why should someone use this feature?
- Project managers and product owners.
What is the underlying (business) problem?
- Poor UX for project managers and product owners that are trying to understand at a glance how well the project is tracking.
How do you use this feature?
Use cases
Who is this for? Provide one or more use cases.
- Project managers and product owners. It's useful to understand what team members are overworked, are behind in their timelines, or what tasks are closer to being completed or not. Gitlab provides some information, but it can be even more helpful.
Feature checklist
Make sure these are completed before closing the issue, with a link to the relevant commit.
- Feature assurance
- Documentation
- Added to features.yml