That really depends on how much management there is for hand holding. I expect a good developer to get a ticket to fix the size of a button and be able to follow up with stakeholders about the size of the button next to it.
It'd be really weird if we sunk so much effort into ticket writing that everything really was just reduced to a task - at that point the ticket author should just go ahead and fix the thing.
It's a symptom of a well organised org. The ticket doesn't need to have a lot of detail (unless your ticketing system is dysfunctional and forces you to input a lot of information, which is sadly more common than it needs to be), only enough to capture what needs to be done and where so it's not forgotten.
It's no different to filing a ticket with the building management to replace a broken lightbulb - it's in your interest to know whether they replaced it already without having to stand up from your desk to check, and it's in their interest to know which individual problems are located where so that they can plan their weekly maintenance run through the building accordingly.
It'd be really weird if we sunk so much effort into ticket writing that everything really was just reduced to a task - at that point the ticket author should just go ahead and fix the thing.