I once had a ticket to update a field in the ERP system while working in the data warehouse. Their programmers were swamped, and they thought it was a simple process.
I built the update query, tried to run it, and it failed due to a security issue. I talked to the guy running security, and he said I had access. A simple query - changing the case of the entries into upper case as the production crew had loaded them in mixed in a YN field. I had to figure out how to grant myself access, then run it, and then explain to the security officer what he needed to locked everyone out of.
A less than 5 minute job estimate turned into an all day affair. In your ticket example just a count, or in a context of actual verses estimated time, this would appear what a slacker.
Only a few looking at this ticket understood how little reflection it related to the actual task. Only my manager and the security officer understood the value of by my doing it, a hole had been closed as their were about 40 or 50 other people with SME access that could grant themselves the ability to update anything in production. This was the true measure of value of the task done - the ticket only noted I had done a ‘simple’ task and took way too long.
One thing rarely documented in these ticket systems - time you spend on automating something that business does manually, and how much savings add up over time. You may spend 4 hours once creating something that if they only spend 10 minutes a day on, shows where the true value lies.
As you well know from experience, numbers are pretty meaningless without enough context.