[sldev] Jira cleanup, giving pjira a little loving

[Robin Cornelius]

The (p)Jira looks in need of a little love,

I didn't like to just wade in there and start resolving bugs on mass so ...

Any objections to going through and closing old bugs for example i
just found this http://jira.secondlife.com/browse/VWR-31, still open,
major and against version 1.13.1.7. And loads of other examples of
this type of report hanging around.

There are swathes of crash after log in that need chucking in a bug
duplicate or need more info pile and other random crashes with no
details so again if these are getting a bit old any objections to
resolving most as duplicate or needs more info.

How old should be considered really stale, for example a login crash
on 1.17.X is probably not relevant on 1.19.X anymore or certainly as a
minimum needs reproducing on latest stable version so should be closed
unless there again is something specific.

Just an idea, if a user reports a bug are they automatically added as
a watcher? there are so many bugs where a user files a crap report
then there is no point asking for more info as they will never check
the JIRA again and are not a watcher so don't get an email so its
immediately a stale bug.

Also is it possible (or could it be possible) to assign issues to
one's self again. Sometimes its nice if i make a bug report or feature
request to mark that i am working on it and its not just a stale
request. I can understand restricting the assigning so you can't just
assign to who you like but to yourself could be useful.

Robin