You are viewing illiterat

James Antill - BugZilla feature of the year -- recent (commented) history

Apr. 29th, 2009

06:57 pm - BugZilla feature of the year -- recent (commented) history

Previous Entry Share Next Entry

Something I've wanted for a long time is "show me the BugZilla tickets which I've looked at "recently" (last day, week, etc.). Like almost everyone else I speak to I get by saving all my bugzilla email and then doing seartches in evolution.

However today ajaxxx found/used advanced bugzilla search options to give a page which has the recent most history of comments you've done. This isn't quite the same as being able to see everything that you've looked at, but it's pretty close.

The url and the saved search

The search works due to two "advanced features: 1. Selecting yourself as the commentator: <field0-1-0=commenter>, <type0-1-0=equals>, and <value0-1-0=%user%> and 2. Selecting comment changes that happened after 8 days ago <field0-0-0=longdesc>, <type0-0-0=changedafter>, and <value0-0-0=8d>. The "8d" part can obviously be changed to reflect different history. To experience the feature a full working URL is: here

I also created a saved search called Commented in last 8 days. You may also want to change your column layout to include the changed time (alas. I don't know of any way to create a custom view for just a single search, *sigh*).

Bonus: search for bad attachment types

Another problem I hit a lot is that python code tracebacks in plain text, but users often leave the "crash" as the default application/octet-stream ... which means it can't be viewed. Really I'd like BugZilla to notice this, and fix it. But after seeing the above search I created: YUM* weird attachments, which searches for any BZ (belonging to the yum group) that has an attachment of type application-octet/stream that isn't obsoleted. Then it's a simple matter of manually fixing the problem bugs.

Update: 2009-04-30 --

Thanks to mcepl, I've now fixed the "shared" links so the should work for everyone != me :).

Comments:

From:mcepl
Date:April 30th, 2009 09:21 am (UTC)

Not so easy and much easier

(Link)
Hi,

a) your link doesn't for anybody else than yourself. I see you have found out already how to make shared queries work, but gave us wrong URL -- https://bugzilla.redhat.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Commented%20in%20last%208%20days&sharer_id=73713 is much better.
b) You can Greasemonkey script for manipulating bugzilla
http://mcepl.fedorapeople.org/scripts/greasemonkey/bugzillaBugTriage.user.js (soon to be in the fedorahosted triage repo), which allows among other things one click conversion of application/octet-stream to text/plain attachments.
(Reply) (Thread)
[User Picture]
From:illiterat
Date:May 1st, 2009 04:34 am (UTC)

Re: Not so easy and much easier

(Link)

I don't have JS enabled on my main browser (which is what I use for BZ), so JS hacks don't work.

Thanks for pointing out the BZ shared searches URL weirdness, is there an easy way to get the "URLs to give other people" ... or do I just paste the above and change the namedcmd part each time? (I tried this on the YUM* URL)


(Reply) (Parent) (Thread)
From:mcepl
Date:May 1st, 2009 07:39 am (UTC)

Re: Not so easy and much easier

(Link)
a) you can have JS enabled in Firefox (of course, not everybody uses Firefox) even if you are super-security conscious if you use NoScript (https://addons.mozilla.org/en-US/firefox/addon/722)
b) just copy them "Run" link from your "Saved Searches" page.
(Reply) (Parent) (Thread)
[User Picture]
From:ajaxxx
Date:May 1st, 2009 01:08 pm (UTC)
(Link)
You can also work around the attachment type problem with this.
(Reply) (Thread)
From:mcepl
Date:January 24th, 2010 03:06 pm (UTC)

One more thing

(Link)
BTW, just to remind you that these actually are not the droids you are after: you haven't found bugs with your week old comments, but bugs where you have commented (whenever) AND where anybody changed any comment in the last week. That's IMHO not the same. Remember, the smallest unit bugzilla thinks in is a bug not a comment.
(Reply) (Thread)