Monitor:Respond 15.2 Planning Issue
Planning Boards
Goals for the milestone:
- Follow-up clean up from deprecation and removal
- Merge remaining FE for Incident Timeline MVC
Capacity
How is Say/Do calculated?
Say Do Ratio = (Do / Say) Do == product issues closed during iteration or had workflowproduction/workflowverification labels applied before iteration end date Say == product issues with Deliverable label and in current milestone during iteration
Milestone | Deliverable issues planned | Deliverable issues delivered | Deliverable issues rescheduled | Say/Do Ratio |
---|---|---|---|---|
14.8 | 9 | 6 | 3 | 66.67% |
14.9 | 9 | 3 | 6 | 33.33% |
14.10 | 6 | 5 | 1 | 83% |
15.0 | 17 | |||
15.1 | ||||
15.2 |
Scope of Work for Engineering
Feature Work
Priority | Issue | Notes | Assigned | In Dev/ Merged | Frontend | Backend |
---|---|---|---|---|---|---|
Priority 2 | Display Incident Timeline Events | workflowin review MR Deliverable | @tristan.read |
|
|
|
Priority 2 | Delete timeline event | backend complete workflowin review MR Deliverable | @rkadam3 @tristan.read |
|
|
|
Priority 2 | Add timeline event manually | workflowin review MR Deliverable |
|
|
|
|
Priority 2 | Add timeline event from comment | backend complete Incident Timeline Iteration Deliverable | @rkadam3 @tristan.read |
|
|
|
Priority 2 | Automatically add Incident timeline event when a certain event occurs | Deliverable | @ck3g |
|
|
|
Priority 2 | Prevent to edit non-editable incident timeline events | Deliverable | @ck3g |
|
|
|
Priority 2 | Follow-up from "Prevent to edit non-editable incident timeline events" | Deliverable | @ck3g |
|
|
|
Priority 2 | Edit timeline event | backend complete Incident Timeline Iteration Deliverable |
|
|
|
|
Priority 2 | Documentation for Incident Timelines | Done, ready to merge. gitlab-org/gitlab!88641 (merged) Deliverable | @rkadam3 |
|
|
|
Priority 4 | Incident Tag MVC | MVC is just start and end time of incident, we can pull more scope in as needed |
|
|
|
Planned Maintenance
Includes planned maintenance work, bugs, and technical debt.
Priority | Issue | Notes | Assigned | In Dev/ Merged | Frontend | Backend |
---|---|---|---|---|---|---|
Priority 1 | Tracing Clean-up | Follow up from 15.0 tracing removal | @rkadam3 |
|
|
|
Priority 1 | Tracing: Cleanup database of project_tracing_settings | Deliverable |
|
|
|
|
Priority 1 | Tracing: Remove backend application code | Deliverable |
|
|
|
|
Priority 1 | Tracing: Remove UI at Settings > Monitor > Tracing and left nav item | Deliverable |
|
|
|
|
Priority 1 | Tracing: Remove UI at Monitor > Tracing and left nav item | Deliverable |
|
|
|
|
Priority 1 | Tracing: Deprecate usage ping & snowplow metrics | Deliverable |
|
|
|
|
Priority 1 | Logging Clean-up | Logging clean-up following up from removal in 15.0 | @rkadam3 |
|
|
|
Priority 1 | Deprecate and remove the Elastic-stack chart | Deliverable |
|
|
|
|
Priority 1 | Logging: Cleanup database of `clusters_applications_elastic_stacks` & `clusters_integration_elasticstack` tables | Deliverable |
|
|
|
|
Priority 1 | Logging: Delete backend code for configuring logging via Elastic Stack | Deliverable |
|
|
|
|
Priority 1 | Logging: Deprecate usage metrics for ElasticStack cluster installation | Deliverable |
|
|
|
|
Priority 1 | Logging: Delete backend code for viewing pod logs | Deliverable |
|
|
|
|
Priority 1 | Logging: Delete UI code for configuring logging via Elastic Stack | Deliverable |
|
|
|
|
Priority 1 | Logging: Delete UI code for viewing pod logs | Deliverable |
|
|
|
|
Priority 2 | Increase Apdex SLI urgency | Follow-up work on Apdex Error Budget Improvement |
|
|
|
|
Priority 3 | Adding a todo for an incident via the incident route fails | typebug | @rkadam3 |
|
|
|
Priority 4 | Remove & cleanup managed alerts backend CRUD code | typemaintenance |
|
|
|
|
Priority 4 | Follow-up from "Remove extra GraphQL query when loading alert list" | typemaintenance |
|
|
|
Unplanned Maintenance
Includes priority1 severity1 issues, Engineering Allocation, and Borrow.
Priority | Issue | Notes | Assigned | In Dev/ Merged | Frontend | Backend |
---|---|---|---|---|---|---|
Priority 1 | Confidential | security Deliverable |
|
|
|
|
Priority 1 | Confidential | security Deliverable | @syasonik |
|
|
|
Scope of Work for UX
Scope of Work for Product
Issue | When it should be ready |
---|---|
- 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