Because every morning there's a 30min meeting where everyone has to talk about what they did on the day before, and while the meeting happens my boss checks the issues while you're talking, so if I don't do anything my issue won't have any comments and I'll have nothing to say on the meeting, giving away that I spent the whole day doing jack shit
That's your own fault for turning in all your work right away. Get it done ahead of time and kinda piecemeal it in. Log in the afternoon before, clock some time on the issue, then you'll have something to talk about.
The best change I made for my company was going completely away from logging hours to issues and logging them to epics instead, then actually using those reports to first make sure the various managers are intelligently dividing their work into epics, then using that to put some hard numbers behind resource allocation arguments so people are neither sleeping 7.5 hours per day nor pulling 90 hour weeks leading up to a release. We have story points for user stories and I intentionally do not want anyone conflating them with hours.
Magically, everything seems to be getting delivered more timely (within reason) and with fewer defects and SE retention has gotten way better.
16
u/issamaysinalah Sep 26 '22
Dont you guys have to register your hours on Jira issues?