In a lot of cases "this looks bad, fix it" is the correct response. If you look at a problem from a naive engineering standpoint and imagine the mountain of work it would be necessary to fix it and then weigh that against the seriousness of the problem before ever lodging a bug report you'll probably decide that a lot of problems aren't worth fixing, and thus aren't worth even mentioning.
But this is wrong. You always need to keep aware of all the defects and problems with your system even if you have no intention of fixing them now, or ever. Having a thorough understanding of the limitations of your system can give you the impetus for a redesign. And it can also give you the clarity to be able to push for fixes to these problems in the future after redesigns, likely for completely different reasons, make the solutions tractable. Otherwise you just end up in an increasingly deepening pit of mediocrity that you never escape from while your competition pulls farther and farther ahead.