I've worked in places which required every hour worked to be accounted for. This was slightly annoying, but also surprisingly informative sometimes. We usually ended up on accounting the time by the project basis, but I can imagine doing this on the ticket basis, especially if tickets are on the bigger side.

Of course with full time accounting, you want to either have some of "overhead" ones ("self-improvement", "lunch", "mandatory training", "all-hands meeting", "writing down all the tickets"), or you silently inflate logged time of real tasks to account for the overhead.

(I can also imagine some sort of dystopian organization where clueless product managers push the feature tickets, and management requires everyone to only work on the tickets. This sounds pretty nasty, but I don't think it will last for long - either the system will collapse from lack of maintenance, or people will start to pad the tickets. "Yes, it was absolutely necessary to upgrade node.js to the latest version in order to change background color of the login button. There was no other way")