If you think about the problem, discuss it, and then implement the solution properly, it's only one ticket. But if you make a half-assed solution, change it twice, and fix seven related bugs, that is ten tickets, with a potential to make even more tickets in the future.
In practice, if I write my own ticket, some manager will give it a priority 2. And the tickets with priority smaller than 1 never get done, because there are always enough tickets with priority 1, i.e. those written by the management. A few years later, when the project is decommissioned, the tickets with priority lower than 1 are still in the backlog. Of course, if having your ticket in the backlog makes you happy, just go ahead and make one.
It is not how it should be done, in theory. Knowing that does not help much.
There's tickets I know we'll never get to, but things we do actually have time for get real attention, with enough focus and resources to do whatever solution is actually correct. There's often tradeoffs for time, but they're ones we have real input in.