...
Tapping the banner navigates the user to a Runs list screen, 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. |
...
 |
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.
...
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.
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
The user can tap the “Post update” button on the Run Details screen.
Behavior:
A modal appears similar to what happens in the webapp. It should have text at the top informing the user where this update will be posted. There should be a text field for adding in the status update. This field should be focused by default and be pre-populated with the template or the last update, as it works in the web app.
There should be another field for the
Timer for next updateand it should have a default value selected as per the playbook configuration. The user can edit this value by selecting any of the other options in the dropdown menu.Note: the user will not be able to set a custom timer for the next update in this MVP.
Finally, there should be a checkbox to
Also mark the run as finishedsimilar to the webapp.Once the user is done typing the update, they can tap on the
Postbutton in the top right to post the update.
Result: The update is broadcast to the relevant channels as configured in the playbook.
Edge case: If the user taps the
Postbutton with no text in the status update, there should be an error and the field should be highlighted.
Tasks & Checklists
The lower portion of the Run Details screen shows tasks, grouped by checklists. This section will show all tasks in the run for the MVP, irrespective of whether they are unchecked, checked, or skipped.
...
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.
Check Off a Task
...
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
...
Note: Test on iPad with Split view as well.
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.
...