Please do not use "fixed" as the default status for issues (as seen here on drupal.org). This only creates confusion and (because one doesn't always notice this and leaves it "fixed" instead of setting to "active") many many bugs do not get the atention they deserve. Still worse, they're (seemingly) automatically closed after a few days of having the status "fixed", which is very bad.

Comments

Anonymous’s picture

Anonymous (not verified) commented
Title: Do not use "fixed" as default status for issues! » Do not use "fixed" as default status for issues on drupal.org!
Project: Project » Drupal.org site moderators
Component: Issues » web site

Recategorizing in the hope to get more attention. Please set "active" as the default status for issues on drupal.org. I'm slowly getting tired of changing the status of newly submitted issues from fixed to active... TIA, Uwe.

TDobes’s picture

TDobes commented

for reference: There was a duplicate.

oc’s picture

oc commented

Yes, this is something on the web site which should be easy to fix, and which definitely would make it easier for people submitting issues as well.

junyor’s picture

junyor commented

Also see http://drupal.org/node/10984 and http://drupal.org/node/15725.

Anonymous’s picture

(not verified) commented

Another duplicate - http://drupal.org/node/16012

Yet another duplicate - http://drupal.org/node/16025 (tangent made a patch in this one - http://drupal.org/files/issues/issue.inc.defaultstatus.patch )

tangent’s picture

tangent commented

Why is this bug submitted against the web site? That implies that Drupal.org should have a different implementation than the "project" module. Anyway, lets just get (attached to my other bug linked by the previous poster) submitted and move on.

Is there any argument against changing this default?

TDobes’s picture

TDobes commented

The patch from this issue was committed and this now appears to be fixed.

Anonymous’s picture

(not verified) commented