Objective
Better organize playbook steps and stages so that they are easier to track during a workflow.
Update UX to reflect the recent polishes.
Assumptions
Only deployed to Cloud alpha users.
Requirements
Must be able to… | User Story | Jira Issue | |
|---|---|---|---|
| 1 | Create stages when editing a playbook | As a playbook member, I can 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. | |
| 5 | Hide completed steps | As a workflow member, I only see steps yet to be performed by default in the right-hand sidebar but can still access completed steps so that it is easier to understand what I should be doing next. |
User interaction and design
Open Questions
Question | Answer | Date Answered |
|---|---|---|
How/if doe the UI support the use cases of “I thought a step was complete but just found out it’s actually not”? | ||
How/if does the UI support the use case of “this step from the playbook turn out to be not relevant to the workflow. How do I get rid of it? (convo link) | ||
Since slash commands are effectively async, should we simplify step states to just yes/no for now? | ||
What level of Markdown support is there for playbook and step descriptions? |
Out of Scope
Enable users to repeatedly run the slash command for a workflow step via RHS.