launchpad-dev team mailing list archive

[Julian Edwards <julian.edwards@xxxxxxxxxxxxx>]

On Thursday 14 October 2010 22:27:11 Ursula Junque wrote:
> On Thu, Oct 14, 2010 at 4:57 PM, Robert Collins <
> 
> robert.collins@xxxxxxxxxxxxx> wrote:
> > On Fri, Oct 15, 2010 at 6:13 AM, Julian Edwards
> > 
> > <julian.edwards@xxxxxxxxxxxxx> wrote:
> > > On Thursday 14 October 2010 05:35:46 Robert Collins wrote:
> > >> I'm going to add a tag 'pg83' to all the existing timeout bugs; if
> > > 
> > > Did you mean to remove the timeout tag at the same time or is that an
> > > accident?
> > 
> > It was deliberate,  per the zero oops policy they are meant to be
> > tagged with only 'timeout' - or so I was request by Ursula a couple of
> > months back.
> 
> This is because the tag 'timeout' implies OOPS, as timeout is a category of
> OOPS. So we keep the 'oops' tag for exceptions, and 'timeout' for timeout
> OOPSes. If one wants to know all bugs that are OOPSes (any OOPS), combining
> both tags in a search should work. Is this not working for (plural) you?

If the interface to search for multiple tags were easier I'd agree, but as it 
is I find it painful.

As an example, this is what I do to find "oops":

1. Go to https://bugs.edge.launchpad.net/soyuz
2. Click on the "oops" tag in the tag cloud.  Easy!

To search for multiple tags:

1. Go to https://bugs.edge.launchpad.net/soyuz
2. Click on "Advanced search"
3. Scroll the page down to get to the tag input box
4. Manually type tag names (error-prone)
5. Forget that I need to set some more status checkboxes at the top and scroll 
back up to do so
6. scroll back down and click search

So in summary, I'd find it really useful if we could keep all relevant tags on 
bugs.  If it's just policy not to, I'd like to recommend changing the policy.  
However, if there's a good technical reason to keep it as it is then fair 
enough.

Cheers.