Objective
Enable Playbooks to auto-add people to channels on incident start so that it saves user from repeating the same taskBetter organize playbook steps and stages so that they are easier to track during a workflow.
Assumptions
Requirements
Must be able to… | User Story | Jira Issue | |
---|---|---|---|
1 | Specify in the playbook a list of users to be added to the channelCreate stages when editing a playbook | As a playbook editormember, I can specify the people and bots to get added every time so that it saves incident participants time when executing. | |
2 | Specify in the playbook a channel of which all members will be added to the incident channel | As a playbook editor, I can specify the list of people and bots to get added based on specific channel membership so that it can be dynamically determined based on the situation. |
| 3 | Send outgoing webhooks on change events | 4 | Expose documented REST API | 5 | Enable unrestricted developer use while requiring enterprise license for production use | As a developer, I can run the Incident Response plugin in my sandbox and consume its APIs so that it’s easy to build integrations. |
...
edit playbook to section the checklist of steps into stages so that a long list of steps is more manageable. | |||
2 | Set active workflow stage | As the workflow owner, I can change the stage that is currently active so that it is displayed by default for workflow members in the right-hand sidebar. |
|
3 | View steps in stages during a workflow | As a workflow member, I can switch between the stages in the right-hand sidebar during a workflow so that I can review what has been done and coming up. | |
4 | Assign step owners | As a workflow member, I can assign a step in the workflow to a specific member so the allocation of responsibility is clear in the right-hand sidebar. |
User interaction and design
...
Open Questions
Question | Answer | Date Answered |
---|---|---|
...