There are some types of bugs which are very hard to reproduce, happen very rarely and seemingly by random. It can happen, that I find a possible cause, fix it, test the program, and can't reproduce the bug. However, as it was impossible to reliably reproduce the bug and it happened so rarely, how can I indicate this in a bugtracker? What is the common way of doing it?If I set the status to fixed, and the solution to fixed, it would mean something completely fixed, wouldn't it?Is it common practice to set the status to fixed and the solution to open, to indicate to the testers, that it's probably fixed, but needs more attention to make sure ?Edit: most (if not all) bugtrackers have two properties for the status of a bug, maybe the names are not the same. By status I mean new, assigned, fixed, closed, etc., and by solution I mean open (new), fixed, unsolvable, not reproducible, duplicate, not a bug, etc.
How to handle bugs that I think I fixed, but I'm not entirely sure
testing;issue tracking
Is it common practice to set the status to fixed and the solution to open, to indicate to the testers, that it's probably fixed, but needs more attention to make sure?Common or not, this is the right thing to do anyway, and you laid out why yourself: no matter how, it is a good approach toindicate to the testers, that it's probably fixed, but needs more attention to make sureSide note even if particular bug tracker does not have field like one you describe as solution, developer can at least add a free-form comment explaining above....and if bug tracker does not allow to add comments to the issue then it must be replaced with one that does. Ability to add free-form clarifications is a critically important feature since issues vary too much to fit into some pre-defined form.