Customize Issues Tab

[GoogleCodeExporter]

The Issues tab does not contain a "Pending" state which will allow any
project member to make an issue as resolved, without actually closing it.

Dan should customize the entire Issues tab so that it meets the needs of
the project.

Original issue reported on code.google.com by matt.van...@gmail.com on 20 Jan 2008 at 8:42

[GoogleCodeExporter]

Issues tab has undergone a first wave of customization. Suggestions are 
welcome, but 
I think these labels will fit our need.

Original comment by Daniel.S...@gmail.com on 21 Jan 2008 at 1:56

• Added labels: Subject-Site

[GoogleCodeExporter]

Original comment by Daniel.S...@gmail.com on 21 Jan 2008 at 2:03

• Changed state: Assigned

[GoogleCodeExporter]

Dan, these tags and other changes look good to me.  I think this can be closed. 
 How
do you want to handle that?  What should our process be?

Original comment by matt.van...@gmail.com on 21 Jan 2008 at 5:35

[GoogleCodeExporter]

Actually, one additional comment.  The PENDING status is a CLOSED type, and I 
think
it should be an OPEN type.  This matches what SFEE does, which is not an 
argument in
and of itself, but it seems to me that the pending state means that the issue 
is not
yet closed.

Original comment by matt.van...@gmail.com on 21 Jan 2008 at 5:39

[GoogleCodeExporter]

I want to give users a chance to see that issues have been resolved and are 
PENDING 
before they go to CLOSED and 'disappear' from the issues list. I'm thinking 
about 
moving a wave of PENDING issues to CLOSED once a week. Like weekly maintenance. 
Let 
me know what you think about that...

Original comment by Daniel.S...@gmail.com on 22 Jan 2008 at 4:03

[GoogleCodeExporter]

Original comment by Daniel.S...@gmail.com on 22 Jan 2008 at 4:04

• Changed state: Pending

[GoogleCodeExporter]

Original comment by Daniel.S...@gmail.com on 26 Jan 2008 at 9:03

• Changed state: Closed