← back to cases
case
your launch is in three days — qa found a bug in a non-critical path
the challenge
qa found a bug in the bulk export feature. it corrupts CSV output when the dataset has more than 10,000 rows. the happy path (export under 10k rows) is clean. the corrupted output doesn't lose data — it scrambles column ordering, which means any customer with custom scripts built against the export format will break. you have three customers who regularly export over 10k rows. you do not know if any of them use custom scripts. all three are in your enterprise tier.
the launch is Tuesday. it was announced to customers last week. your CEO mentioned it in a customer call. fixing the bug is a two-day engineering task, and your lead engineer is finishing a different critical bug that would block the launch entirely if unresolved.
// what would you do here?
0 takes
no takes yet. be the first.