I wonder what other questions we can ask ourselves about bug stories. 
What was the root of the problem?
Who could have helped spot it?
How much impact has it really had?
Who did it impact?
What processes should be reviewed?
What can we learn from it?
Yes, great questions!
And I found this handy set of post-mortem questions.
Some that stood out that I think are particularly helpful:
We used to do a thing called âFive Whysâ following any production incident that required a notification to users of a degraded experience. The purpose of the technique is to promote a root cause analysis and then generate a corrective action. Like many of these kinds of ceremonies it feels awkward at first. But over time it gets better.
Global McDonald outage:
In New Zealand, X user Germin van Royen: âThe Mcdonalds outage is crazy. Went in tonight and drive thru + all kiosks were down. A system that can fail nation wide is bad but across multiple countries too!? Bonkers.â
In other news, citizens of those countries were reported to be slightly healthier than those in countries where McDonaldâs did not fail.
(Yes, thatâs sarcasm)
âSainsburyâs says it will not be able to fulfil the âvast majorityâ of online deliveries on Saturday because of âtechnical issuesâ.â
Yikes, feeling for team Sainsburyâs. 
This one is a true national crisis. If this doesnât raise the profile of software and systems issues nothing can.
Anonymous reviews that werenât actually anonymous, oops.
Triage closed the bug reports âBy Designâ
that is no âoopsâ
Itâs âoopsâ on the part of whoever made that design decision.
I might consider using the site to look for jobs, but thereâs no way Iâm posting anything there.
I like it:
it is possible to insert two receipts into TICO machines
That was a feature, not a bug, and allowed gamblers to redeem two receipts and be paid the aggregate amount.
But a software glitch meant that the machines would return one of those tickets and allow it to be re-used â the barcode it bore was not recognized as having been paid.
Iâm dream-guessing that someone in the dev team thought, we canât allow redeeming two receipts, thatâs a bug, and thought of âfixing itâ. Redeem one and reject the other. Especially based on âAn internal investigation found ânumerous failures (human, process and technological) that more than likely prevented the fraud from being identified at an earlier opportunity.ââ
I hope that this one is not a airline any of us have used.
Hereâs a boundary bug with an airline not liking people over 100 years old 
Found via @bethtesterleeds on LinkedIn
As far as Iâve experienced this limitation(max 99 years) is present on a larger scale in aviation.
This might be handled differently per system: error in the interface when booking a flight or allowing the booking and dealing with it after.
Lol iâve used them quite a lot actually and not come across this but something tells me i may try this on BA. 
There is the famous Aviation case of computer software being âinfallibleâ, that was used as case-law in the Post Office Scandal of a chinook crash, which involved GPS coordinates calculations or something being wrong Faulty software could have caused Chinook crash in 1994 | Military | The Guardian