Time is double-spent on meetings and other tasks
Maybe this can go here, under "Avoid/reduce some of the activities which are hard to log."
I see that 121 meetings (and other interactions) are sometimes logged on the same ticket. Let's say devs A and B have a 1-hour 121 meeting regarding ticket T, which as a time estimate of 8h. Both log their time on ticket T. Now there's a remaining time of 6h. This is double spending of the time estimate, and it only makes sense if the sum of all logged time on T is the sum of all time put into T, and NOT the time we expect T to be completed in.
I'd suggest a special category of tickets for meetings, discussions and other hard-to-log activities; and it should be easy to find, so I don't have to dig up an ancient ticket AA-xxx which my mentor took the time to show me it exists.