Comments on: Bugzilla Reports for MediaWiki

By: Arturas

Arturas — Fri, 28 Oct 2011 06:22:41 +0000

Hello,
I have one problem and don’t know how to fix it. I can’t start using bugzilla reports on my mediawiki. My bugzilla version is 3.4.4 on virtual server, mediawiki is on another virtual server. I get this message:
BugzillaReports : Can’t get database connection (user@192.168.0.235) :
Warnings were generated during the execution of function

Setting parameter bzalternateconfig is not supported
Getting parameter bzalternateconfig is not supported

By: Ian Homer

Ian Homer — Mon, 11 Apr 2011 23:08:43 +0000

Matthew – thanks for the positive feedback, glad you’re finding it useful. Unfortunately the extension doesn’t support AND of keywords. The building up of the keywords and subsequent SQL search is in http://code.google.com/p/bugzillareports/source/browse/trunk/BugzillaQuery.php if you’re feeling like you want to dive in.

By: Matthew

Matthew — Mon, 11 Apr 2011 21:10:58 +0000

Hello, awesome extension Ian! I think I might be overlooking something obvious here. For the keywords field, is it possible to make the search use AND instead of OR? So similar to
|keywords=testing,help,beta
except that it will only return bugs id’s where ALL three of those keywords were present?

By: Ian Homer

Ian Homer — Tue, 10 Aug 2010 09:29:23 +0000

Glad, that helped. On the custom fields, sorry, but the custom field filtering is currently limited to equality check.

By: David D

David D — Mon, 09 Aug 2010 17:22:54 +0000

Thanks Ian, you are correct. Its actually using current php version on “old” mediawiki. Gotta love php. Its fixed and the extension is working fine. Great job!

next question:

A lot of our reports depend on a few custom fields. I see that i can run queries based on custom fields with the “filter=” option, but it only supports equals (=). I need to test if a custom field is greater than a defined value. Is this possible?

By: Ian Homer

Ian Homer — Sat, 31 Jul 2010 09:31:00 +0000

It might be related to a conflict with your php version and mediawiki core – see http://code.google.com/p/bugzillareports/issues/detail?id=41 where there’s a work around described

By: David D

David D — Fri, 30 Jul 2010 21:32:18 +0000

the line in BugzillaReports.php

70 $wgParser->setFunctionHook( ‘bugzilla’, ‘efBugzillaReportsRender’ );

results in

Parameter 1 to Language::getMagic() expected to be a reference, value given in [...]/userwiki/mediawiki-1.15.3/includes/StubObject.php on line 58

By: David D

David D — Fri, 30 Jul 2010 21:04:01 +0000

this is embarassing, but I’ve followed all the instructions, and still all I get is the verbatim “{{#bugzilla:}}” text on my wiki page. Versions of mediawiki and bugzilla are up to date, I’ve tested the db connection, and the extension is even correctly listed on my wiki’s version page. What noob thing am I missing to get mediawiki to actually use the extension as it should?

By: Ian Homer

Ian Homer — Mon, 31 May 2010 21:04:27 +0000

Barak – I’ve copied the post on your issue to a new ticket called “closed=-1w not working in standalone mode” @ http://code.google.com/p/bugzillareports/issues/detail?id=55 … it’ll be easier to sort this out their without overloading these blog replies

By: Barak

Barak — Sat, 29 May 2010 21:45:06 +0000

Another question – why the generated SQL contains this in the where clause: and bug_status’CLOSED’ ? A reminder, I’m looking for bugs closed in the last week.