Commit 5d024bc2 authored by drew stachon's avatar drew stachon 👋
Browse files

Add direct link to top-flaky-test-file issues with 24h SLOs

parent 7a3a00b7
Loading
Loading
Loading
Loading
+1 −1
Original line number Diff line number Diff line
@@ -232,7 +232,7 @@ Pipeline Execution has a few special workstreams of unplanned, reactive work tha
- [Pipeline Execution Infradev Triage and Tracking](https://gitlab.com/gitlab-org/verify-stage/-/work_items/635)
- [Pipeline Execution S1 & S2 Bug Triage and Tracking](https://gitlab.com/gitlab-org/verify-stage/-/work_items/619)
- [Pipeline Execution RFH Triage and Tracking](https://gitlab.com/gitlab-org/verify-stage/-/work_items/614)
- [Pipeline Execution Flaky Tests](https://gitlab.com/gitlab-org/verify-stage/-/work_items/637)
- [Pipeline Execution Flaky Tests](https://gitlab.com/gitlab-org/quality/test-failure-issues/-/work_items?sort=created_date&state=opened&label_name%5B%5D=automation%3Atop-flaky-test-file&label_name%5B%5D=group%3A%3Apipeline%20execution&first_page_size=20): Any open issues with these labels not already in Verification need to be picked up (In Dev) and be moved to Verification in < 24 hours.

These issues can be scheduled for work at any time, based on their triaged severity. S1 issues may be pulled directly into development, and some issues could be backlogged or closed outright if the issue requests changes that we're not going to make. Regardless of the triage outcomes, these issues need to be _addressed_ promptly, and not left in the backlog. If there is a developer directly assigned to an issue, they should be the first point of contact and authority on the resolution of that issue. In general, the EM and PM will be responsible for ensuring these get resolved within our target timeframes.