24 строки
2.4 KiB
JSON
24 строки
2.4 KiB
JSON
{
|
|
"checklists": [
|
|
{
|
|
"items": [
|
|
{
|
|
"title": "Untitled task"
|
|
}
|
|
],
|
|
"title": "Default checklist"
|
|
}
|
|
],
|
|
"create_channel_member_on_new_participant": true,
|
|
"create_channel_member_on_removed_participant": true,
|
|
"description": "Customize this playbook's description to give an overview of when and how this playbook is run.",
|
|
"message_on_join": "Welcome! This channel was automatically created as part of a playbook run.",
|
|
"metrics": [],
|
|
"reminder_timer_default_seconds": 604800,
|
|
"retrospective_enabled": true,
|
|
"retrospective_template": "### Summary\nThis should contain 2-3 sentences that give a reader an overview of what happened, what was the cause, and what was done. The briefer the better as this is what future teams will look at first for reference.\n\n### What was the impact?\nThis section describes the impact of this playbook run as experienced by internal and external customers as well as stakeholders.\n\n### What were the contributing factors?\nThis playbook may be a reactive protocol to a situation that is otherwise undesirable. If that's the case, this section explains the reasons that caused the situation in the first place. There may be multiple root causes - this helps stakeholders understand why.\n\n### What was done?\nThis section tells the story of how the team collaborated throughout the event to achieve the outcome. This will help future teams learn from this experience on what they could try.\n\n### What did we learn?\nThis section should include perspective from everyone that was involved to celebrate the victories and identify areas for improvement. For example: What went well? What didn't go well? What should be done differently next time?\n\n### Follow-up tasks\nThis section lists the action items to turn learnings into changes that help the team become more proficient with iterations. It could include tweaking the playbook, publishing the retrospective, or other improvements. The best follow-ups will have a clear owner as well as due date.\n\n### Timeline highlights\nThis section is a curated log that details the most important moments. It can contain key communications, screen shots, or other artifacts. Use the built-in timeline feature to help you retrace and replay the sequence of events.",
|
|
"status_update_enabled": true,
|
|
"title": "Example Playbook",
|
|
"version": 1
|
|
}
|