"JIRA bankruptcy", is what I've heard it called. It's an idiotic way to sweep problems that still exist under the run. I have no idea why its so hard for suits

"JIRA bankruptcy", is what I've heard it called. It's an idiotic way to sweep problems that still exist under the run. I have no idea why its so hard for suits to just ignore a list of bugs that isn't even intended for them in the first place. … I also had to fight (and mostly lost) the argument that "time to page getting resolved" was not meaningful. People would be chastised for having pages open too long. But, then, e.g., one page was because the underlying problem was real, and it was a problem in our cloud provider — one that our cloud provider couldn't fix. (They wanted us to just abandon the instance of that service we had, and migrate everything out of it. Problem was is that that was difficult, and expensive. Several months of work. We ended up having to do it. But that destroys a Goodhart "mean time to resolve" metric.) But people can process "you have to look at it on a case by case basis, and see if there was a good reason for it", as, Christ, that requires thinking! There was also metrics around hitting SLO, and the SLO was bananas. In theory, we were supposed to do a post-mortem if we missed the SLO. But the SLO got missed so often that, in reality, nobody did the PMs. (And in fact, it effectively killed the culture of "writing PMs" that had existed… and now problems don't really get addressed.) … and I agree about the managers/PMs. When engineering has no authority, the resulting crap isn't surprising.