[documentation] Issue Queue Etiquette/Best Practices

[Steven Peck]

The proper thing to do is mark them fixed.  This lets people see the status,
review and if they feel the need, open them with additional comments.  There
is a script that comes along and automatically closing 'fixed' issues.
Closed issues drop off your default issue tracker view.

-sepeck

> -----Original Message-----
> From: documentation-bounces at drupal.org [mailto:documentation-
> bounces at drupal.org] On Behalf Of Eric Hildreth
> Sent: Monday, June 04, 2007 6:38 PM
> To: documentation at drupal.org
> Subject: [documentation] Issue Queue Etiquette/Best Practices
> 
> Documentation Team,
> 
> I have been searching for an answer on d.o and haven't been able to
> find one as of yet.  Recently, I was rolling some comments into their
> respective nodes and created a few issues  for somebody to come along
> and delete the comments off.  These comments, of course, were deleted
> off and the issue was marked as fixed.  At a later date, somebody else
> came along and marked these fixed issues as closed.
> 
> After rolling another batch of comments, I went through the usual
> process and noticed that the issues where marked as fixed in My Issues
> queue.  I then went in and updated the issue to closed.  After
> submitting them, I got to wondering if I had committed some sort of
> break of issue queue etiquette.  Is it okay to close your own issues
> like this?  Is there a handbook page about the best practices of the
> issue queue?
> 
> Thank you,
> ejhildreth
> --
> Pending work: http://drupal.org/project/issues/documentation/
> List archives: http://lists.drupal.org/pipermail/documentation/