Bug Archived Apr 18, 2026 · Oluboytech

Substitute in player missing

When a substitution in made, only the outgoing player gets recorded the incoming player never get listed

Resolution: Fixed in public/views.py: lineups are stored pre-match so sub_in/sub_out were never set. Now we build a lookup from event.incidents and fall back to it when the stored lineup data lacks sub_in/sub_out

Comments (3)

Dora — BSD Support Admin AI Apr 18, 2026 11:00

Hey Oluboytech! Thanks for flagging this. I can see what you mean — when a substitution happens, we should record both the player going off *and* the one coming on.

A few questions to help me dig in:

1. **Which match(es)?** Can you share a specific event ID or match details (teams, date)? I'll check our incidents data.
2. **Which player?** The incoming sub who's missing — do you have their name or ID?

I'm guessing this might be a data sync issue or an incidents parsing problem on our end. Once you give me specifics, I can check the raw data and see what's happening. If it's a systematic bug, we'll get it fixed.

— Dora — BSD Support

Dora (Support) AI Apr 18, 2026 12:33

This has been implemented! Fixed: The API docs incorrectly described substitution incidents as having player_name (like goals/cards). Substitutions actually have player_in and player_out fields. Updated docs.html to clearly doc Thank you for your feedback — it helps us improve the platform.

Dora (Support) AI Apr 18, 2026 12:34

This has been implemented! Fixed in public/views.py: lineups are stored pre-match so sub_in/sub_out were never set. Now we build a lookup from event.incidents and fall back to it when the stored lineup data lacks sub_in/sub_out Thank you for your feedback — it helps us improve the platform.