@jo_shih@vincywilson@at.ramya when you have a moment, could you please review the open issues to determine which fall under your areas, and then either mark yourselves or someone on your teams as DRI? If there are any without a DRI once you're all done with your reviews, I will help figure out who should own.
@tpazitny - Sorry I missed this earlier. I think BE would be the DRI for gitlab-org/gitlab#250572 (although it's labelled as both backend and ~Quality). How should we proceed with that issue?
Tanya Pazitnychanged the descriptionCompare with previous version
changed the description
Tanya Pazitnychanged the descriptionCompare with previous version
changed the description
Tanya Pazitnychanged the descriptionCompare with previous version
changed the description
Tanya Pazitnychanged title from FY22-Q3 KR: Reduce the number of Quality corrective action issues from 7 to 0 to FY22-Q3 KR: Reduce the number of Quality corrective action issues from 4 to 0
changed title from FY22-Q3 KR: Reduce the number of Quality corrective action issues from 7 to 0 to FY22-Q3 KR: Reduce the number of Quality corrective action issues from 4 to 0
Tanya Pazitnychanged the descriptionCompare with previous version
changed the description
Joanna Shihchanged the descriptionCompare with previous version
@tpazitny I noticed that gitlab-org/gitlab#280585 (closed) was removed from this KR after the engineering allocation labels were applied there. Does that mean it is going to be handled in a separate process or should I (continue to) ask the access group to prioritise it?