64898b2c79
Some checks failed
Code scanning / CodeQL (push) Failing after 15s
Zulip production suite / Ubuntu 22.04 production build (push) Failing after 26s
Zulip production suite / Debian 12 production install with custom db name and user (push) Has been skipped
Zulip production suite / Ubuntu 22.04 production install and PostgreSQL upgrade with pgroonga (push) Has been skipped
Zulip production suite / Ubuntu 24.04 production install (push) Has been skipped
Zulip production suite / Ubuntu 26.04 production install (push) Has been skipped
Zulip production suite / Debian 13 production install (push) Has been skipped
Zulip production suite / 7.0 Version Upgrade (push) Has been skipped
Zulip production suite / 8.0 Version Upgrade (push) Has been skipped
Zulip production suite / 6.0 Version Upgrade (push) Has been skipped
Zulip production suite / 10.0 Version Upgrade (push) Has been skipped
Zulip production suite / 9.0 Version Upgrade (push) Has been skipped
Zulip production suite / 12.0 Version Upgrade (push) Has been skipped
Zulip production suite / 11.0 Version Upgrade (push) Has been skipped
GitHub Actions Security Analysis with zizmor / zizmor (push) Failing after 3s
Zulip CI / Debian 12 (Python 3.11, backend + documentation) (push) Failing after 26s
Zulip CI / Ubuntu 22.04 (Python 3.10, backend + frontend) (push) Failing after 3s
Zulip CI / Ubuntu 24.04 (Python 3.12, backend) (push) Failing after 25s
Zulip CI / Ubuntu 26.04 (Python 3.14, backend) (push) Failing after 25s
Zulip CI / Debian 13 (Python 3.13, backend) (push) Failing after 28s
Zulip production suite / Required jobs (push) Has been cancelled
Zulip CI / Required jobs (push) Has been cancelled
API Documentation Update Check / check-feature-level-updated (push) Has been cancelled
API Documentation Update Check / notify-if-api-docs-changed (push) Has been cancelled
26 lines
1.7 KiB
JSON
26 lines
1.7 KiB
JSON
{
|
|
"action": "create",
|
|
"createdAt": "2023-04-11T10:21:34.858Z",
|
|
"data": {
|
|
"id": "c7cafc52-994d-4984-a217-bff9f9aa9473",
|
|
"createdAt": "2023-04-11T10:21:34.858Z",
|
|
"updatedAt": "2023-04-11T10:21:34.858Z",
|
|
"body": "Performing a thorough impact analysis and cost realization is a crucial step in responding to any system outage or incident. By examining the extent of the outage, the affected systems or services, the number of users impacted, and any error messages or logs generated during the incident, we can gain a comprehensive understanding of the scope of the incident.\n\nThis information can then be used to prioritize the resolution efforts and minimize the impact on our organization's operations. Additionally, cost realization allows us to evaluate the financial impact of the outage on our organization and make informed decisions regarding resource allocation for future incidents.\n\nOverall, conducting a thorough impact analysis and cost realization can help us effectively manage incidents and prevent similar issues from occurring in the future.",
|
|
"issueId": "f9a37fcf-eb52-44be-a52c-0477f70e9952",
|
|
"userId": "674c90c8-35ea-454d-8ca4-5548258fd795",
|
|
"reactionData": [],
|
|
"issue": {
|
|
"id": "f9a37fcf-eb52-44be-a52c-0477f70e9952",
|
|
"title": "Thorough Impact Analysis and Cost Realization"
|
|
},
|
|
"user": {
|
|
"id": "674c90c8-35ea-454d-8ca4-5548258fd795",
|
|
"name": "Satyam Bansal"
|
|
}
|
|
},
|
|
"url": "https://linear.app/webhooks/issue/WEB-46#comment-c7cafc52",
|
|
"type": "Comment",
|
|
"organizationId": "7a661544-df08-4cd1-a1e3-5ec611898806",
|
|
"webhookTimestamp": 1681208494995
|
|
}
|