Add On Call Scheduling to Incident Management Capabilities
Problem to solve
As a developer who is on call, I would want the ability to use GitLab to schedule my on call rotations, so I can spend less time setting up schedules in external applications, catch errors faster (rather than have an external tool receive the issue and alert), and further consolidate the time I have to switch from GitLab to other tools.
Intended users
- Ethan (Software Engineer)] (https://about.gitlab.com/company/team/#eurie)
- Rajat (Software Engineer)] (https://about.gitlab.com/company/team/#rajatgitlab)
- Donald (Engineering Manager)](https://about.gitlab.com/company/team/#donaldcook)
User experience goal
This solves the issue of needing to use an external applications to manage on call scheduling. With this consolidation of tooling users will save time from switching between applications, and develop further familiarity and understanding of the GitLab application.
Proposal
Add on call scheduling capabilities under the Operations section of GitLab.
Mockup
Further details
All prominent incident management platforms utilize scheduling as a key capability:
Permissions and Security
Only managers should have the capacity to modify schedule.
All users should have the capacity to view the schedule.
Stakeholders should also have the ability to view scheduling (this can prove an important selling point).
Documentation
Availability & Testing
What does success look like, and how can we measure that?
Measure success by usage of scheduling within the platform by overall users, aiming for 2% of users within GitLab using scheduling by end of quarter 4 2021.
What is the type of buyer?
Buyer Personas: Engineering Manager, CTO, Manager, SRE, DevOps Lead, IT Manager.
Tier: Premium and Enterprise tier.