Extension talk:Bugzilla Reports

BugzillaReports is a wonderful extension that does exactly what it says on the tin, and does it really well! Our organization have been using this extension since its release and we find it invaluable. Nice one Ian!

Geoff Parkes, Vet-One.co.uk, 2008

ExtensionDistributor
Currently, Bugzilla Reports isn't listed in Special:ExtensionDistributor. Could it be added? --Catrope 16:48, 15 July 2008 (UTC)


 * Sure, but I'm not sure how that list of extensions gets generated. Do you know if it's driven from the main MediaWiki SVN repository? --Ian Homer 21:26, 16 July 2008 (UTC)

Using same bz db connection as mediawiki one
A bug was reported which threw the php exception (not a valid MySQL-Link resource) below. This occurred when you use the same bz db connection as the mediawiki one.

sql_real_escape_string: 41 is not a valid MySQL-Link resource

This has been fixed and will be released in v0.9.1 (coming very soon) --Ian Homer 08:20, 14 August 2008 (UTC)

Bugzilla 3.2
Can someone confirm that this still works with bugzilla 3.2?

Yes, it still works with Bugzilla 3.2 [mailto:philippe.lambot@mil.be Philippe Lambot]

Time restriction
Is there a posibility to restrict the output to the Bugs changed within the last n days? --Joergens.mi 10:56, 9 December 2008 (UTC)

Try "modified=-3d", e.g.

--Ian Homer 23:59, 9 December 2008 (UTC)

Bug creation
Is there a way to get a report of all the bugs created by person X within the last N days?

-- DaveO 2/28/09


 * Not quite, but you can generate all bugs that were created by person X and which were modified in the last N days - .  Not the quite the same thing - although it will include all the bugs in that were created by person X within the last N days, but it may include others.  If you feel you need the report for "all bugs created by person X within the last N days" could you raise it @ http://code.google.com/p/bugzillareports/issues/list? --Ian Homer 18:38, 1 March 2009 (UTC)
 * You can now do this in v1.1 (beta) - e.g. --Ian Homer 13:36, 24 June 2009 (UTC)

Testopia
It would be nice to integrate this extension with the Bugzilla addon Testopia --189.128.39.211 19:12, 28 March 2009 (UTC)


 * Sounds an interesting idea - bugzilla reports is now in google code @ http://code.google.com/p/bugzillareports/issues/list - could you raise this in that list and put a few more details around what you'd like to see.  If you have skills in this area, the source is all open and I'd welcome patches to cover new features like this --Ian Homer 20:26, 28 March 2009 (UTC)

Writing number of returned bugs into the variable
Hello,

Is it possible to write the number of returned bugs (rows) to the variable, e.g. using #vardefine ? Then i'd like to use this variable in #expr.

Thanks


 * Yes, try the example below (you'll need to take v1.1 beta to get this to work) --Ian Homer 13:30, 24 June 2009 (UTC)

Dynamic Filters to bugs
hello, is it possible to implement dynamic filters for a table generated using this extension. so that one could drill down based on the requirement. Thank you


 * Not sure I understand what you mean by dynamic filters. The arguments can be taken from parameters (e.g. product=) or other MediaWiki extensions, (e.g. product=) - is this what you are looking for --Ian Homer 12:22, 1 August 2009 (UTC)

SQL error when using "|closed= "
Hi! I have an error when I'm using |closed=, e.g. closed=-1w:

BugzillaReports : Error running the sql : SELECT DISTINCT bugs.bug_id as id, alias, closedactivity.bug_when as closed, quickflag.flagdate as flagdate, priority, products.name as product, bug_severity as severity, bug_status as status, short_desc as summary, bug_file_loc as url, version FROM bugs LEFT JOIN (SELECT bug_id, MAX(bug_when) as bug_when from bugs_activity where fieldid= and added='CLOSED' GROUP BY bug_id) as closedactivity on bugs.bug_id=closedactivity.bug_id LEFT JOIN (SELECT bug_id as quickflagbugid, MAX(creation_date) as flagdate from flags where status='?' group by quickflagbugid) as quickflag on quickflag.quickflagbugid=bugs.bug_id LEFT JOIN products on bugs.product_id=products.id where 1=1 and closedactivity.bug_when >='2009-07-28' and bug_status<>'CLOSED' order by priority,bug_status ASC; ERROR: syntax error at or near "and" LINE 1: ...en) as bug_when from bugs_activity where fieldid= and added=...

Could you please,help? In this way I wanted to know the number of closed bugs per week. Thank you!


 * Yep I spotted this the other day and fixed under http://code.google.com/p/bugzillareports/issues/detail?id=33&can=1 - just tested on our local system and it works OK.  If you want to pick up the fix for this you'll need to take the release from trunk as described @ http://code.google.com/p/bugzillareports/source/checkout since this fix has not made it into a release yet --Ian Homer 22:33, 4 August 2009 (UTC)

"Warnings Were Generated ... Report Truncated Count Greater than Max", etc...
We're migrating our bug database from Test Track, and have imported them into bugzilla with hopes of integrating into our in-house wiki. I have created a report which returns only two records (which agrees with Test Track), keeping it simple and specifying only the component name. Works fine until I add 'lastcomment=1', at which point I get the above message and only the first record.

Since I can link to the actual bugzilla listing, losing the details is not a big deal, but the 'hover bubble' is a cool feature and it would be nice to have it working.

I have tried bumping up the $maxrowsFromConfigDefault (to as much as 1000!) but while this allows the report to complete and display both records, I still get the message. These entries have A LOT of text in their description fields, but there are only two actual records. Is this a bug, or just new user error?

A great extension - much simpler than writing out all the queries using SQL2wiki or the like.

Thanks! Mickeyf

Oops - I discovered the 'troubleshooting' section at the bottom of the page. I have pasted the SQL into phpMyAdmin, it does not generate any errors, but does generate 1362 rows. In the log I note that of the 1362 rows generated, apparently two are being pulled out for rendering.


 * That looks like a bug. The report truncation is designed so that an administrator can put a cap on how big reports can get, but given that you've upped the $maxrowsFromConfigDefault AND that the behaviour only happens when you add "lastcomment=1" then it's clearly not behaving well. It might be that the counting of the numbers of rows is amiss since this may be counting all the rows with all the joins (of which only a couple of rows are relevant for your report).   Log it @ http://code.google.com/p/bugzillareports/issues/list and I'll review this area of the code --Ian Homer 22:57, 18 August 2009 (UTC)