As long as the reporter can attach table schemas (presumably also created in-code) and data (which can be loaded by the code... presumably) then sure yeah. It's a lot better than having to ask for versions and reproduction cases that don't often come automatically.
> Plus, having to deploy code from the ticket just to be able to reproduce a bug seems like a huge PITA. Give me the local execution!
Ideally the code could be deployed automatically -- perhaps only from trusted/internal parties depending on the product -- so you don't have to actually do that much work. Less than you would if you had to create a database with the specific flags and environment exactly matching those of the reporter.
I dunno, I dream of this sort of reproducible bug report. I don't like the "what version" "what queries" "what errors" back and forth that always seems to happen, even with internal users.
> Plus, having to deploy code from the ticket just to be able to reproduce a bug seems like a huge PITA. Give me the local execution!
Ideally the code could be deployed automatically -- perhaps only from trusted/internal parties depending on the product -- so you don't have to actually do that much work. Less than you would if you had to create a database with the specific flags and environment exactly matching those of the reporter.
I dunno, I dream of this sort of reproducible bug report. I don't like the "what version" "what queries" "what errors" back and forth that always seems to happen, even with internal users.