"H.Merijn Brand" wrote:
>
> On Wed, 21 Feb 2001 17:26:52 +0100, Richard Foley <[EMAIL PROTECTED]> wrote:
> > > > > I don't think that if we're going on on this road, *any* of the smokers would
> > > > > be interested in ack's, wouldn't we?
> > > > >
> > > > > category=configure
> > > > > status=incapable
> > > > > severity=low
> > > > > ack=daily
> > > > >
> > > > ack=no
> > >
> > > I know, but it was a suggestion to use the category for what it's meant for and
> > > /still/ be able to see it was from daily.
> > >
> >
> > Is the answer here to use more than one category?
> >
> > category=configure
> > category=dailybuild
> > ack=no
>
> I like that, but how would you select on either? Would every ticket get 1+
> category fields?
>
Do you mean both?
I see no reason not to have more than a single category, for example
where a regex bug hits you at compile time from somewhere deep in the
core:
category=core
category=regex
category=compile
In most cases this won't be necessary (at the moment you can't do it),
but it could be useful in some circumstances.
status=open
status=closed
and
severity=low
severity=high
Is not allowed of course, but I see no reason why
osname=irix
osname=linux
should not be ok, etc.
So we could make a special case - or rather lots of special cases...
:-(
Or the category could be a multiple selection box
:-)
I've just finished modifying the database to allow for multiple
categories<->bug and the same with most other factors, which would allow
this to happen, and be far more useful in the future (I think). This
will be in the next release, but I have a couple of bugs to iron out
first before I install it :-)
Ciao
--
Richard Foley
Ciao: shorter than Aufwiedersehen
