User tags for the BTS were announced by aj here: http://lists.debian.org/debian-devel-announce/2005/09/msg00002.html
Comments about usertags can go on this page...
from #debian-mentors:
<pabs3> ooh, usertags <pabs3> bts++ <Nigel> pabs3: i thought it was a random users suggestion at first, was about to reply, "HAHAHA, they will never do that" <pabs3> :) <pabs3> aj does roxor <Nigel> yeah <Nigel> i must go and set usertags on all my bugs now... <Nigel> i must say the following though: it'd be nice for the maintainer to get a copy of all tags set... <pabs3> yeah, indeed <Nigel> also, it'd be nice if there was a link up the top now, with "Maintainers Tags" <Nigel> or (dunno if this defeats the purpose) set it up so tags set against the maintainer's email address, or the package@packages.d.o addy shown by default... <pabs3> even better, add a thing to reqest@ for advertising usertags by default for a certain user/package/etc combo <pabs3> adding it to the wiki page :)
- After playing around with usertags a bit for the purpose of using them for tracking bugs about non-DFSG-free documentation, here some thoughts about further improvements:
One could add a option to the CGI to select a predefined categorisation class. I would like to say something like
Example 1: ...;class0=Status;nam1=myown;pri1=...;ttl1=...;class2=Severity
Another useful addition could be to be able to globally rearrange the ordering of the categories. If I have used example 1 and now I want to rearrange the categorisation to move Severity to the top level I currently would have to do that (we assume for a moment the class parameters would actually work):
Example 2: ...;class1=Status;nam2=myown;pri2=...;ttl2=...;class0=Severity better: ...;class0=Status;nam1=myown;pri1=...;ttl1=...;class2=Severity;ord=1,2,0
Here my first tries with categorisation together with usertags:
by ?FrankLichtenheld
I've started to use usertags to track QA issues, using "proposed-{removal,orphan}" on bugs that I've filed on very old and rc-buggy packages. At the moment, I'm using [http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=proposed-orphan,proposed-removal;users=debian-qa@lists.debian.org;nam0=Status;pri0=tag:proposed-removal,proposed-orphan;ttl0=Proposed%20to%20be%20removed,Proposed%20to%20be%20orphaned;nam1=Severity;pri1=severity:critical,grave,serious,important,normal,minor,wishlist;ttl1=Critical,Grave,Serious,Important,Normal,Minor,Wishlist,Unknown%20Severity;ord1=0,1,2,3,4,5,6,7 this] to track my bugs (as they were filed yesterday, I don't have much experience yet). It's quite useful, but the long URIs are not ideal, so I second Frank's request for a way to specify standard classifications in a shorter way.
It would also be very nice to use the package a bug is filed against to divide them into sections. I'd like to use something like this:
tag=proposed-orphan,proposed-removal; users=debian-qa@lists.debian.org; ... nam1=Status;pri1=pkg:ftp.debian.org,wnpp; ttl1=Pending removal,Waiting for adoption,No answer yet; ord1=2,1,0
by ?MarcBrockschmidt
Couldn't we show the usertags of packagename@packages.debian.org by default on the BTS site of packagename? Like this the maintainer could categorise the bugs with a set of his own tags and all users could see them.
(This is done.)
I've created a page, OngoingTransitions, that tracks library transitions in unstable. It'd be nice to have support for classifying by "is there a tag by this user set?", in order to separate claimed bugs (by bugsquash@qa.debian.org ).รง
--?AdeodatoSimo
DebianInstaller uses usertags and usercategories to produce some useful views of our bugs and installation reports. See ["DebianInstaller/Bugs"] for details.
The testing security team tags bugs with their CVE id (ie, CVE-2005-0001) and also uses a "tracked" tag to indicate security bugs that they are tracking and find ones they are not. These tags are added automatically based on info in their database. Set users= debian-security@lists.debian.org to see these tags.
Here's a useful view in the BTS: http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=security;users=debian-security@lists.debian.org;ordering=tracked