[Ubuntu-bugcontrol] Stop triaging bugs

[Brendan Donegan]

IMO, a team should also be looking at Triaged bugs when selecting new
tasks to work on, so if the bugs are genuinely Triaged and they have
enough information to go to In Progress (when a developer wants to work
on them) then I don't see the harm in general. I personally would tend
to look at both New and Triaged bugs when looking to pick up bug fixing
work on the projects I help maintain.

On 26/03/14 03:14, Pierre Equoy wrote:
> On Wed, Mar 26, 2014 at 12:15 AM, Alberto Salvia Novella <
> es20490446e at gmail.com> wrote:
> 
>> El 25/03/14 17:02, Brian Murray escribió:
>>
>>  What particular bug number was this message regarding?
>>>
>> Marc was referring to the following work-flow <http://tinyurl.com/c7wok2e>
>> (security bugs with an status of "new").
>>
>>
> Would it be possible for the security team to update this workflow to:
>     security bugs with status in ("New", "Triaged")
> ?
> 
> That would be a request like this:
> https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&search=Search&field.status%3Alist=NEW&field.status%3Alist=TRIAGED&field.information_type%3Alist=PUBLICSECURITY&field.information_type%3Alist=PRIVATESECURITY&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.component-empty-marker=1&field.tag=&field.tags_combinator=ANY&field.status_upstream-empty-marker=1&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_no_package.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&orderby=-importance&memo=75&start=0&direction=backwards
> 
> (I took the previous one and added issues with a "TRIAGED" status)
> 
> Cheers,
> 
>