Monitor:Respond 15.8 Planning issue
Planning Boards
Goals for the milestone:
- Continue to work towards a production ready MVC for the Slack App for Incident Management
- Arrive in 2023 feeling rested and refreshed!
OKRs for Q4 FY23:
- Increase internal usage (dogfooding) of incident management features
- Increase awareness and engagement around GitLab Incident Management's solution
- More teams use GitLab Incident Management
Focus for the Milestone
Team member focus for the milestone.
Engineer | Issue |
---|---|
Kristen Cutler | Wrapping up gitlab-org/gitlab#347500 (closed) and gitlab-org/gitlab#376760 (closed). Thinking gitlab-org/gitlab#345063 |
James Rushford | Add anchor to an incident timeline |
Paulina Sedlak-Jakubowska | Additional event tags & incident highlight bar. Plus some cleanups in the meantime |
Peter Leitzen | |
Rajendra Kadam | All things Slack. |
Tristan Read | Clean up presentation of items in incident high... (gitlab-org/gitlab#360009) |
Vitali Tatarintev | Since the milestone is kinda short because of the holidays, I think I'll focus on adding incident management related functionality to GitLab CLI. Besides that, I think I can start working on adding system notes on linking/unlinking alerts. |
frontend, 61% of backend)
Capacity: 56% (48% ofMore details...
-
frontend: max of 3 engineers, 28 days in milestone
40(days) = 84 - 31(PTO) - 1(Borrow) - 12(Onboarding)
-
backend: max of 5 engineers, 28 days in milestone
85(days) = 140 - 38(PTO) - 9(Borrow) - 8(Onboarding)
Data from: Monitor:Respond Update Calculator, Monitor:Respond Group Calendar
Scope of Work for Engineering
Feature Work
Slack App
-
Phase 1: Introduce incident-specific Slack noti... (gitlab-org/gitlab#367550 - closed), Phase 1
of Manage incident updates through Slack (gitlab-org&8806) backend M -
Phase 1: Add `/slack <channel>` quick action to... (gitlab-org/gitlab#345063), Phase 1
of Manage incident updates through Slack (gitlab-org&8806) backend M -
Phase 1: Add `/gitlab incident comment <text>` ... (gitlab-org/gitlab#374957), Phase 1
of Manage incident updates through Slack (gitlab-org&8806) backend L
Incident Timeline
-
Introduce additional tag types for incidents (gitlab-org/gitlab#360315 - closed) frontend S -
Clean up presentation of items in incident high... (gitlab-org/gitlab#360009) backend S frontend M -
Capture and display incident duration (gitlab-org/gitlab#360005) backend S frontend S -
Add a link in the toast message that takes you ... (gitlab-org/gitlab#372287) frontend M
Post-incident Reviews
%15.7
Rollover from-
Introduce related alerts to incidents (gitlab-org/gitlab#356057 - closed), backend frontend -
Widgetize Severity sidebar component (gitlab-org/gitlab#351629 - closed) frontend
Maintenance
Planned
Includes planned maintenance work, bugs, and technical debt.
Unplanned
Includes priority1 severity1 issues, Engineering Allocation, and Borrow.
No unplanned maintenance as of December 9th, 2022
Seeking Community Contributions
Issues that are great candidates for community contributions. These include the labels Seeking community contributions, ~"Accepting merge requests" or ~"good for new contributors".
-
Incident timeline UI cleanup - improve spacing (gitlab-org/gitlab#384237 - closed), frontend -
Incident timeline UI cleanups - subscription fo... (gitlab-org/gitlab#384239), frontend -
Alert activity feed is broken (gitlab-org/gitlab#383131 - closed), frontend -
Bug Timeline Event side border when creating ne... (gitlab-org/gitlab#384023 - closed), frontend -
The close/reopen buttons at the bottom of an in... (gitlab-org/gitlab#343237), frontend, severity4 -
Don't allow duplicate resource links (by URL) i... (gitlab-org/gitlab#377831), backend -
User can create on-call rotation with negative ... (gitlab-org/gitlab#332474 - closed), frontend, backend, severity4
Scope of Work for UX
Issue | When it should be ready |
---|---|
Ensuring the issues in Scheduled Overrides (gitlab-org&5311) are designreadyforeng | 15.9 |
Stretch: On-Call Schedules allow for specific days (gitlab-org/gitlab#355807) | 15.9-10 |
Scope of Work for Product
-
Create and publish the 3️⃣ rd blog post in the Incident Management Blog Post Series -
Establish a pipeline of customers and users to interview, https://gitlab.com/gitlab-org/monitor/respond/-/issues/176+ -
Create a teardown for GitLab Incident Management in a blank state for Reporters, Developers and Maintainers and identify opportunities to help users better onboard with GitLab Incident Management.
-
Set the Milestone (current Milestone) -
Update the Milestone link for the Monitor:Respond Planning Board -
Set the Due Date for the end of the current Milestone
Edited by Tristan Read