If this had hit us.. we would just switch to excel or something for a week/month?
But maybe we are a very light user of JIRA. Nothing in there can't be replaced. It's "nice" to be able to go look up a 3 year old bug and which client reported it, but not really crucial for day to day ops.
He didn't say it was sufficient; he said they could do it for a short while. I consider myself in the same situation: we depend on Jira, but for a week or so it's not a big deal to use a bunch of Post-It notes.
I don't see this as a valid comparison. There is information loss. This has happened to my team which had about 50 people and it was very chaotic. It took us several days to just create the state our features were in.
Today it would even be more troublesome as we have a lot of integration rules dependent upon the workflow. I'd probably just recommend everyone uses a few weeks for self improvement and only address critical production issues.
On prem is worse in some cases. If you don't have access to the source code or ability to modify it, you're still at the mercy of someone else and now there's likely additional hoops to jump through.
If your Oracle DB or Cisco router has a software big, you can always restore/rebuild but that doesn't guarantee you won't hit it again and in both cases you're still at the mercy of the company producing it.
Even if you're on OSS are you able to fix a data corruption bug yourself?
You get more control over maintenance windows and backups, but it doesn't automatically guarantee better uptime.
