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

[Alberto Salvia Novella]

If it brief, perhaps it isn't that bad.


El 06/11/13 20:08, AG Restringere escribió:
>
>     It [Launchpad] already creates a full history.
>
>
> There are some drawbacks to that:
>
>  1. It doesn't tell me which Bug Control/Squad team members are
>     creating activity on the bug.
>  2. The "summary" button is at the bottom of the page and on really
>     long bug reports I wont even notice it's there, it also opens up
>     to a separate web-page which takes me away from the bug-report.
>  3. It provides too much information, when all I needed was a brief
>     summary.
>  4. It doesn't create anything useful that can be made searchable.
>
> The "activity summary" would:
>
>  1. Tell me which Bug Control/Squad team members are creating activity
>     on the bug.
>  2. Be located at the very top of of the bug report in the header on
>     top side-bar so I can see it immediately, it would be on the same
>     page as the bug-report.
>  3. Provide just a brief summary of triage activity, not a full list
>     of actions.
>  4. Create bug triage activity data that can be searchable via
>     Launchpad so I can find bugs that aren't getting enough attention.
>      This is also really valuable for other reasons like analysis and
>     getting an overall visualization on bug activity.
>
>
>
>
> On Wed, Nov 6, 2013 at 1:39 PM, Dr. David Alan Gilbert 
> <ubuntu at treblig.org <mailto:ubuntu at treblig.org>> wrote:
>
>     * AG Restringere (ag.restringere at gmail.com
>     <mailto: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 <http://treblig.org> |                
>                   | In Hex /
>      \ _________________________|_____ http://www.treblig.org   |_______/
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20131106/afed12de/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2260 bytes
Desc: Firma criptogr??fica S/MIME
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20131106/afed12de/attachment-0001.bin>