I work at a place where if you have too many "open tickets", you get a message from someone in a managerial position telling you that you have too many open tickets ("thanks, I did not know that!"). The kicker is, however, our ticket assignment works on a best-fit basis, and I dip my hands in enough stuff a lot of cases are assigned to me, and I don't mind. What I do mind though, is having to close tickets just to close tickets to fill someone else's absurd and abstract and useless bottom-line. But the managers don't seem to understand the difference between closing tickets and helping people. I don't close tickets before the case is resolved, and I don't care that there is a ticket assigned to me five years ago about a GPU virtualisation problem that may have gone stale 2 years back when NVIDIA, bless their heart, updated their drivers. I can't attend to the ticket on a whim, and it's on a long back-log, but I _know_ the problem may still be there which is why I keep the ticket assigned to myself. And so on.
I am pretty sure Google has the same problem as I attribute to our work place (just to be clear, no I do not have a problem with too many tickets, we're storing garbage 100x the volume these tickets require as upkeep, and in a year it will be 100x more for the former).
This. From the article: "but there is no cost to keeping them around." This is true from a holistic POV of a software project as a whole. This is /not/ true for an individual in an organisation who wishes to remain employed and whose performance review depends on arbitrary metrics.
A few years back, when $CORP employed management consultants to streamline their operations, I discovered my red line: I refused point blank to lie in Jira to make graphs go in the direction the consultants needed them to instead of the way that painted an accurate picture of reality. I kicked up a huge fuss and quit over this. No-one else did - not because they agreed with the consultants, but because I was the only person on the team who was in a stable enough position to survive walking away.
I do not blame people for wanting to live in a house and maybe occasionally eat.
are these issues only you can fix? i agree that any single developer should not have to many issues assigned to them. but it depends what assigned means/ to me it means that only the assigned person and noone else is going to work on this. consequently at one company where i worked, issues did not get assigned until the person started to actively work on them. everything else was in a general pool that no one in particular was responsible for, at best with tags of who or which team this might be relevant to.
I think it’s partially a philosophic question of “what is the purpose of a bug / ticket tracker?”
Some people treat their ticket list as a historic record of defects found, whether or not they are being actively worked on or whether or not there is even a plan to fix them. To these people, the bug list is documentation of all the software’s issues.
Other people treat the bug list as their work checklist. Tickets are a working set of things we are actively working on and plan to resolve. If you don’t have a plausible plan to fix the bug, you close it as “won’t fix”.
I find camp 1 just accumulates and accumulates and the bug list becomes this long menu that you have to periodically groom and pick from. I happen to fall in camp 2 and am very aggressive about closing things that will realistically never be fixed. My bug list is what I actually have a plan to resolve.
When you get both camps in one company, it gets confusing and you end up with these “bankruptcies.”