I feel like it is perhaps not a "good look" to repeatedly try to sell your product in your writeup about your product's catastrophic outage atlassian.com/engineering/po…
- I feel like it is perhaps not a "good look" to repeatedly try to sell your product in your writeup about your product's catastrophic outage atlassian.com/engineering/po…
> To manage the restoration progress we created a new Jira project.... This approach empowered all teams to easily identify and track issues related to any individual site restoration. please don'tanyway if you were hoping to get any sort of insight into how high performance teams respond to high profile business critical incidents, this is not the writeup for youthere is nothing substantive in this writeup, just the usual superficial gloss about how smart and careful they are and how they will be even *more* smart and careful in the future
Yes the write up smells of PR. It has some decent details hidden in charts that need zooming in on the desktop. But the quality and readability is very low, tiers below eg GitHub or Cloudflare post-mortems.Atlassian published their postmorten on JIRA, Confluence, and other sites down for ~400 companies for up to 2 weeks. I'm not happy with the postmortem, as they are hiding the number of actual impacted seats/users. As per my research, 50,000-800,000 users were impacted.
