Reopening incorrectly closed bugs?

[pjc]

Mostly a procedural question so that I do things the most helpful way:

When a bug is closed as "resolved" with an unfounded assumption that it was fixed (and it wasn't), does adding a comment to the bug report cause it to pop up on anybody's radar, or do I need to file a new bug report?

 

[cyberjock]

This question has been asked by me in PM and IRC more than a dozen times. There doesn't seem to be a correct answer except to open another ticket, link to the old ticket, explain that it's not fixed and provide your evidence of such. :)

Unfortunately, this means that you are likely to not see it fixed until the next released after the current one being tested. So yes, improper closure seems to be a death keel for bugs that won't be fixed for a very long time after being reported.

It's not ideal, but it's the best i got. :/ If you look at my bug comments I've made quite a few comments about something not being fixed when the ticket was closed, and they're still closed. :/

Edit: Had to reword slightly. It sounded like *I* had asked this question more than a dozen times. More than a dozen people have asked me this question and the answer above is what I was provided.

 

[jkh]

Mostly a procedural question so that I do things the most helpful way:

When a bug is closed as "resolved" with an unfounded assumption that it was fixed (and it wasn't), does adding a comment to the bug report cause it to pop up on anybody's radar, or do I need to file a new bug report?

Adding comments to a closed bug does indeed pop up on our radars; you don't need to open a new one to get us to notice this. Sometimes, if even that is not enough to get a bug re-evaluated, you can also email bugs-admin@freenas.org and request a re-look. I have re-opened dozens of bugs over the last year when it turns out that we did indeed close one erroneously (sometimes, we even go back to check on something once "new evidence" appears and re-open them ourselves without prompting).

The state of a bug is just a state - it can be changed at any time, the only real difference being that closed bugs (and there are multiple states which map to "closed") don't get reviewed in our weekly bug review meeting every Thursday, so there's still definitely value in arguing a bug back into an open state if you think we genuinely did not fix the problem (now, of course, "not to be fixed" is kind of special - it means we just don't plan to fix it, so arguing in that case may indeed be pointless!).

 

[pjc]

Oops...sorry for the flurry of update spam, in that case. I took cyberjock's advice and reopened a few. My apologies.