By uNeedStuff on

I've noticed that at some point after a support or bug issue has been fixed someone goes through and changes the status to "Fixed". When someone replies, should the initiator change the status to Fixed?

I haven't because I thought the module person would be responsible for that, but maybe it should be me because either my bug is fixed or the support question answered. However I could not find this in the handbook, and was unsure if as a user I should close a issue.

If it is the initiator, possibly that could be added to the documentation as well as changing the title to Issue instead of bug as that is what they are actually called here.

Thanks!
Shari

Comments

dww’s picture

dww
we/he/they
commented

1) there's a cron job that moves issues from "Fixed" to "Closed" after they've been fixed for 2 weeks and there have been no replies. the idea is that once someone marks something fixed, there's a window of time when other people viewing the issue queue will want to still see the issue. perhaps the "fix" actually broke something else. perhaps it's not really fixed yet, etc. after it's fixed, and no one's commented for 2 weeks, it's safe to assume it's "Closed", meaning it's no longer visible by default when querying the issue queue.

so, no, you shouldn't worry about marking issues "Closed" yourself. if the problem is resolved or the feature is implemented, etc, just mark it "Fixed". let the cron job do its magic 2 weeks later. ;)

2) yeah, the docs about how to use the issue tracker on drupal.org are pretty lacking. they could use the same kind of thorough re-thinking and re-organization that we gave to the CVS handbook (http://drupal.org/handbook/cvs) a few months ago, and that is currently underway for the patch handbook (http://drupal.org/patch).

___________________
3281d Consulting