...
Runs will be accessible from within the channel linked to that run. There are a few different places where Runs linked to a channel will be surfaced.
Runs
...
icon button in Channel Header
Whenever there are in-progress runs linked to a channel in which the user is a participant, a banner an icon button at the top of that channel indicates “X runs in progress”. If there is just 1 run in progress, the banner should say “1 Run in progress”appears with a count for the number of runs in-progress.
If no runs are active, the banner icon button is hidden by default.
Tapping the banner icon button navigates the user to a Runs list screen modal, filtered specifically for that channel.
...
| Info |
|---|
A banner in the channel header adds some complexity and can compete for space with other elements like the bookmarks bar, active call banner, and the new messages banner. We can consider showing an icon with a number in the header as an alternative to the channel banner.  Highlighting new runs We can optionally show an unread indicator on the runs icon button whenever there is a new run that the user has not seen yet.  There might be technical complexities in defining and tracking when a run should be marked as ‘viewed’. From a UX perspective, here’s what it can mean to mark a run as viewed:
|
Channel info modal
If there are any in progress OR finished runs linked to a channel, there’ll be a menu item in the Channel info modal to access Playbook Runs. The menu item should not be visible if there have never been any runs linked to that channel.
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.
...
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.
Runs list
Once the user selects “Playbook runs” (via banner, modal, or bottom sheet), they arrive at a screen listing all runs tied to that channel.
...
For the MVP, we can sort runs by recently updated.
| Info |
|---|
Too many runs For finished runs, the list will keep growing over time as there is usage. We should consider a lazy loading mechanism here and only load ~20 runs at a time, and then load more as the user scrolls. There can be a loading indicator added at the bottom when the user scrolls down to the end.  |
Viewing Run Details
When the user taps a run card, they see the Run Details screen which is similar to the Run RHS in the web app.
...
Run name
Run summary
Owner and Participants (read-only for MVP)
Update due in …
Post Update button
Checklists and tasks
Finish run button
Posting an Update
...
Once confirmed, the run is marked as finished, an update is posted to the relevant channels, and the run is no longer displayed in the In Progress runs screen.
...
Tablet and iPad Support
| Status | ||||
|---|---|---|---|---|
|
It is essential for all these features to work as well on Tablets and iPads.
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 | ||||
|---|---|---|---|---|
|
Playbooks has custom message blocks that provide interactive options and contextual metadata for certain messages. On mobile, these custom messages may have limited functionality based on the available feature set.
...
Note that links within the status update should be tappable.
Status Update Reminders
...
Tapping Post Update immediately navigates the user to that run’s “Post Update” modal.
Selecting a Snooze duration offers a bottom sheet with preset intervals (15 mins, 30 mins, 1 hour, 1 day, 1 week) to delay the reminder. Selecting any of these options should delete the update reminder message and schedule the reminder to be sent after the selected duration.
If offline, the user sees an error toast; the message remains so they can retry.
...
Retrospective Prompt (Run finished notification)
Once a run is finished, the system posts a prompt asking whether to fill out a retrospective report.
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.
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.
...