...
The menu item also shows the number of runs in progress. Tapping on the `Playbook runs` menu item navigates the user to the same Runs list screen for that channel, even if there is just 1 active run in the channel.
When there arr no in-progress runs, the menu item will be there without a number on the right. Tapping on it will navigate the user to the list of Finished runs for the channel.
...
Channel ••• bottom sheet
Similar to the Channel Info modal, if there are any in progress OR finished runs linked to a channel, there’ll be a menu item in the bottom sheet to access Playbook Runs. Tapping on the `Playbook runs` menu item navigates the user to the same Runs list screen for that channel, even if there is just 1 active run in the channel.
...
Once the user selects “Playbook runs” (via bannerthe header icon button, modal, or bottom sheet), they arrive at a screen listing all runs tied to that channel.
...
The only action possible on a Checklist group will be to expand or collapse it. Tapping anywhere on the checklist title row should toggle this.
For every task, the title will be shown in 1 line and and the description can be shown in upto 2 lines. Any overflow will be truncated. The full title and description can be seen in the bottom sheet when the user taps on the task details.
Check Off a Task
The user can tap the checkbox in the Run Details view to mark it as complete.
If a task is in the skipped state, tapping on the checkbox should take it to the unchecked state.
...
Note: Test on iPad with Split view as well.
Link Handling for Playbook Runs
| Status | ||||
|---|---|---|---|---|
|
When a run is linked in the channel(e.g., a run link posted in the channel, custom playbooks bot messages mentioned above), tapping the link should bring up the Run Details modal in the mobile app.
If the user lacks permission to view the run, show an error toast.
Custom bot messages
| Status | ||||
|---|---|---|---|---|
|
...
Since the functionality to add a retrospective is not available on mobile, this custom attachment for filling out the retrospective report should not show on mobile. The message to notify users that the run as ended should only contain the text “@user marked Run Name as finished.
Link Handling for Playbook Runs
When a run is linked in the channel(e.g., a run link posted in the channel, custom playbooks bot messages mentioned above), tapping the link should bring up the Run Details modal in the mobile app.
If the user lacks permission to view the run, show an error toast.
Edge Cases
No Connectivity:
If the user attempts to take an action like post an update or check off a task while offline, there should be a clear error message shown to the user. In case of posting an update, any data entered should not be lost and the user should stay on that screen and be allowed to copy the entered text before closing it or regaining connectivity.
No In-Progress Runs:
The runs banner is hidden in the channel. The “Playbook runs” menu item is still present, but filters default to Finished runs.
No runs at all in a channel (In-progress and Finished)
The runs banner and the “Playbook runs” menu items are hidden for the channel. This is because we don’t have the ability to start a run, hence leaving nothing for users to view or an action to take once they go to Playbook runs.
Permission Issues:
If a user is not a participant in a run, they should not see that run in the channel banner or in the playbook runs list. The run should not be counted while displaying the number of in-progress runs for that user.
...