Monitor:Respond 15.6 Planning issue (October)
Planning Boards
Goals for the milestone:
- Complete all
Phase 2
of Create incidents through Slack - Ship Incident Tags MVC
- Finish the Incident Timelines MVC
OKRs for Q3 FY23:
- Increase internal usage (dogfooding) of incident management features
- Increase awareness and engagement around GitLab Incident Management's solution
🚀 Milestone Deliverables
Deliverable | % Complete |
---|---|
Deliverables Workflow Board | % (0 of 4) |
Focus for the Milestone
Team member focus for the milestone.
Engineer | Issue |
---|---|
James Rushford | |
Peter Leitzen | |
Rajendra Kadam | Incident Tag MVC and Slack Slash Command Phase 1 |
Sarah Yasonik | Work through dragging task backlog & transitioning |
Tristan Read | Finish off remaining incident timeline frontend items |
Vitali Tatarintev |
Scope of Work for Engineering
Feature Work
Slack App
-
Phase 2: Add `status` field to Slack incident c... (gitlab-org/gitlab#374965 - closed), Phase 2
of Create incidents through Slack -
Phase 2: Populate Slack incident creation modal... (gitlab-org/gitlab#374966 - closed), Phase 2
of Create incidents through Slack -
Phase 2: Add new endpoint for returning Slack m... (gitlab-org/gitlab#374967 - closed), Phase 2
of Create incidents through Slack, priority1, Deliverable
Incident Timeline
-
Automatically add incident severity changes to ... (gitlab-org/gitlab#375280 - closed), priority1, Deliverable -
Incident Tag MVC Frontend (gitlab-org/gitlab#373854 - closed), priority1, Deliverable -
Incident management timeline event's preview do... (gitlab-org/gitlab#367854 - closed), frontend -
[Feature flag] Rollout of `incident_timeline_ev... (gitlab-org/gitlab#369416) -
Add delete button in edit more for incident tim... (gitlab-org/gitlab#372265 - closed)
Miscellaneous
missed:15.5
-
Add anchor to an incident timeline (gitlab-org/gitlab#367856), @jrushford -
Event timeline form clean-ups (gitlab-org/gitlab#358637 - closed), @tristan.read -
Incident Tag MVC Backend (gitlab-org/gitlab#373853 - closed), @rkadam3 -
Phase 1: Add `/gitlab incident declare` Slack s... (gitlab-org/gitlab#344856 - closed), @rkadam3
Planned Maintenance
Includes planned maintenance work, bugs, and technical debt.
-
Implement the character limit and text truncati... (gitlab-org/gitlab#372289 - closed) -
Add a link in the toast message that takes you ... (gitlab-org/gitlab#372287), workflowblocked by Add anchor to an incident timeline (gitlab-org/gitlab#367856) -
Hide the Edit action on system-generated events... (gitlab-org/gitlab#371528 - closed), priority1, Deliverable -
Create timeline event form resets when validati... (gitlab-org/gitlab#368935 - closed) -
Stop returning alert details in Prometheus Aler... (gitlab-org/gitlab#372115 - closed) -
Audit gitlab-rails dependencies for Ruby 3 comp... (gitlab-org/gitlab#377904 - closed)
missed:15.5
-
Follow-up from "Remove extra GraphQL query when... (gitlab-org/gitlab#361227), @syasonik -
Service Ping metric counts.issues_created_gitla... (gitlab-org/gitlab#365482), @syasonik -
On call schedules - existing participants appea... (gitlab-org/gitlab#328192)
Unplanned Maintenance
Includes priority1 severity1 issues, Engineering Allocation, and Borrow.
No unplanned maintenance as of October 13th, 2022
Scope of Work for UX
Issue | When it should be ready |
---|---|
https://gitlab.com/gitlab-org/gitlab/-/issues/360439+ | 15.7 (for solution validation) |
Define Monitor:Respond UX Roadmap for FY2024 (gitlab-org/gitlab-design#2129 - closed) | 15.8 |
Scope of Work for Product
-
Create and publish the second blog post in the Incident Management Blog Post Series -
Revert Prometheus Alerts Documentation (gitlab-org/gitlab#373301 - closed) -
Add additional logos to Linked Resources (gitlab-org/gitlab#371210) -
Improve text/docs around required permissions f... (gitlab-org/gitlab#347500 - closed)
-
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 Alana Bellucci