Problem
Contributors report time against the tool they used and the activity they performed, so a reviewer cannot tell what the hours produced or whether anything reviewable came out of them.
Solution
A reviewer can see what each reported hour produced, and time spent in calls and chats lands on the change it led to rather than on a row naming the medium. TIME_REPORTING.md currently invites a tool and an activity, which is what produces rows like |Google Meet|sync and plan team workflow|1|. Direction: state in DEV-370 that time is reported on the PR carrying the change, and narrow TIME_REPORTING.md to work that genuinely cannot be a PR.
References
Problem
Contributors report time against the tool they used and the activity they performed, so a reviewer cannot tell what the hours produced or whether anything reviewable came out of them.
Solution
A reviewer can see what each reported hour produced, and time spent in calls and chats lands on the change it led to rather than on a row naming the medium.
TIME_REPORTING.mdcurrently invites a tool and an activity, which is what produces rows like|Google Meet|sync and plan team workflow|1|. Direction: state in DEV-370 that time is reported on the PR carrying the change, and narrowTIME_REPORTING.mdto work that genuinely cannot be a PR.References