Designs for on-call scheduling
Release notes
Problem to solve
As part of https://gitlab.com/gitlab-org/gitlab/-/issues/235995, we developed some initial ideas for on-call scheduling. In #247956 (closed) we will validate those ideas.
In this issue we'll refine the initial ideas further based on our test results and fill in all the gaps so that we're ready to implement in 13.6.
Intended users
User experience goal
User should be able to complete the following tasks:
- Set up an on-call schedule
- Add a rotation to the schedule
- Add an override to the rotation
- Create an escalation policy
Design
On-call scheduling page designs
Full designs + specs + additional details are visible in Figma. But, an outline of the key screens:
| On-call empty state | Adding a schedule modal | Example schedule added | Adding a rotation modal | Rotation added | Adding an override modal | Final schedule |
|---|---|---|---|---|---|---|
 |
 |
 |
 |
 |
 |
 |
Escalation policy page designs
| Escalation policy empty state | Adding a a policy modal | Modal populated | Policy added |
|---|---|---|---|
 |
 |
 |
 |
Prototype where you can click through all the screens.
Surfacing on-call schedules and escalation policies at the project level
| Surfacing escalation policy at the project level - no escalation policy established | Surfacing escalation policy at the project level - project linked to a policy | Possible way to surface on-call schedule on alerts page - if no schedule has been created | Possible way to surface on-call schedule on alerts page - if schedules have been created at the group level |
|---|---|---|---|
 |
 |
 |
 |
Further details
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
Actionable insights from Solution Validation research
Edited by Amelia Bauerly