Post-launch bug ownership unresolved — frontend and backend teams in conflict
Current state
Post-launch bug has no assigned owner. Frontend and backend teams are in a loop.
Observations
- Blockerslack85% conf8h ago
Frontend team: "The dropdown state is being reset on every render — this has to be a backend event firing too often." Backend team: "We checked the event logs — the frequency is correct. This is a frontend debounce issue."
- Action itemslack92% conf3d ago
Engineering Manager Mike Torres was tagged in the Slack thread 3 days ago but has not responded.
- Riskemail90% conf1d ago
Customer support received 14 complaints from enterprise users in the last 48 hours referencing METRO-92.
Recommended action
MEDIUMFollow up required
Directed at Internal owner
Requires approval before sending
Actions
Update: Ownership escalated to Engineering Manager. METRO-92 has been open for 5 days with no assigned DRI. Frontend and backend teams are each attributing root cause to the other. A DRI assignment is required before root cause investigation can proceed.
Timeline
- Blocker created5d agojira
Customer reported bug after launch. No owner assigned at ticket creation.
- Status changedAlex Park4d agoslack
Frontend team opened Slack thread — believes it is a backend config issue.
- External replyPriya Nair8h agoslack
Backend team replied in Slack: "this looks like a frontend race condition to us."
- Went stale7h agojira
No DRI assigned after 5 days. ~200 enterprise users still impacted.