Bug triage activity summary on bug reports (Launchpad)...

[Dr. David Alan Gilbert]

* AG Restringere (ag.restringere at gmail.com) wrote:
> Robert Park: Thank you for the point by point response, yes now I'll feel
> free to jump in on as many bugs as I can even if others are currently
> working on them. I'll know the help is always appreciated.  Bug-triage is a
> more free-flowing collaborative process that just builds. Got it.

The only thing I'd be careful of is to try not to confuse the reporter;
if a triager has asked the reporter to do something then I'd be a little
bit more careful - i.e. I might ask 'can you also get this at the same time'
but I'd be careful not to confuse things.

I'd also not generally go changing statuses if it was assigned to someone.

> > Alberto Salvia Novella:
> >
> > If this feature is implemented, it can be done by just listing the members
> > of specific teams that recently entered the bug; from teams like BugControl
> > or administrator of the mother project.
> >
> Exactly, like a "Bug Triage" activity report summary:
> 
> Whenever a person on the Bug Control/Squad team is creating activity on a
> bug-report Launchpad should automatically write few brief notes somewhere
> about this and if activity dies down for a while like for 15 or 30 days it
> should say "no recent activity".  It should also provide a list of names of
> the people "triaging" the bug.  This should be searchable so we could find
> bugs that have low Bug Triage activity and need attention.

It already creates a full history.

Dave

-- 
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    |       Running GNU/Linux       | Happy  \ 
\ gro.gilbert @ treblig.org |                               | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/