On Sun, Feb 24, 2008 at 11:58:49AM -0800, Don Armstrong wrote:
> It almost sounds like you want a user setable severity-like field.
> That could be implemented, but the problem is that it's far less
> flexible than usertags because it would only have a single value.
(Note that I did not ask for that, I just followed the line of thought
I've read on the post I replied to. But indeed yes, I think a "priority"
field, which is severity-like would be a good idea, of course the value
space would be different, can even just be a number or something such.)
Yes, it would be less flexible, but what meaning has a priority field
with multiple values? I think that such a field would be meaningful only
to sort upon it, and go looking for sorting of multiple valued fields
seems to be looking for trouble to me.
> In fact, assuming the assignment to usercategories was done properly,
> it wouldn't matter if a bug had multiple "priority" tags, as a bug
> that had the higest tag would be separated from the other tags even if
> it still had a lower tag.
Sounds like hackish, doesn't it?
Anyhow, another point for preferring a non-user priority tag is that you
don't need to set a user, which IMO makes a lot easier to deal with bug
reports since you don't risk to forget what the "right" user for the
tag/category you're setting is (which frequently happens to me).
Cheers.
--
Stefano Zacchiroli -*- PhD in Computer Science ............... now what?
zack@{upsilon.cc,cs.unibo.it,debian.org} -<%>- http://upsilon.cc/zack/
(15:56:48) Zack: e la demo dema ? /\ All one has to do is hit the
(15:57:15) Bac: no, la demo scema \/ right keys at the right time
Attachment:
signature.asc
Description: Digital signature