Solution validation for on-call scheduling
Release notes
Problem to solve
As part of https://gitlab.com/gitlab-org/gitlab/-/issues/235995, we defined an initial proposal for on-call scheduling. In this issue, we will validate these proposals with users to see whether or not they meet their needs.
Intended users
Immediate focus:
- Our internal SRE, Support and Security teams
More generally:
User experience goal
Teams can successfully create and update on-call schedules and escalation policies.
Proposal
Test the prototype with internal team members to see:
- If what we're proposing meets their needs
- If anything important is missing from what we're planning
- If our assumptions about how we're structuring this are accurate
- Figure out what we can do to improve this feature in the short, mid and longer terms.
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
Edited by Amelia Bauerly