Quantcast
Viewing latest article 6
Browse Latest Browse All 6

How should I approach bugs that I know will never be solved?

Occasionally I'll find a bug that is so minor, so miniscule, so unimportant that I know it will get buried under all the high priority bugs. The bugs I find in the application are things like "The Tab order between two items is reversed" in the face of the occasional "Opening the application twice and spinning around three times counter clockwise will set your computer on fire" bugs. I have a growing backlog of bugs that will never get solved, and there is some work involved not just for me in every "fluff" bug I write, but also for others. My team has to triage the bug, and it has to be considered with every iteration whether it will be picked up to be fixed.

While I understand that such careful scrutiny shows that 1.) I'm paying attention to detail and 2.) I'm testing the application, it doesn't seem from my end like I'm bringing much value to the company.

How should I approach bugs like this?


Viewing latest article 6
Browse Latest Browse All 6

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>