Bugzilla Reports for MediaWiki
June 28th, 2008 by Ian HomerHi - I’ve just released an update to the bugzilla reports extension for MediaWiki - see BugzillaReports @ MediaWiki. We use this internally and find it very useful for generating slice and dice reports of our activities. Feel free to give it a try and contact me if you have any questions.
Related articles
Tags: mediawiki
July 10th, 2008 at 6:15 pm
Is your bugzillareports extension compatible with postgresql
July 10th, 2008 at 6:39 pm
Hi Ryan - thanks for the question. Unfortunately it is isn’t compatible with postgresql (yet), if there was sufficient demand I’d happily get it done, although I’m keen to get to the v1.0 out (with the functionality that others have requested) before I move on to cross DB support.
(post edit - 24/07/08) - it now supports PostgreSQL - see http://www.mediawiki.org/wiki/Extension:Bugzilla_Reports
July 10th, 2008 at 8:59 pm
Just had another request for postgresql support - so I’ll make sure it gets done. It’ll probably be a few weeks … but it’s firmly on my todo list now.
July 11th, 2008 at 2:46 pm
Hey Ian, I just wanted to see if there’s any interest on your part in merging the following mediawiki extensions into one:
http://www.mediawiki.org/wiki/Extension:BugzillaReports
http://www.mediawiki.org/wiki/Extension:BugSquish
http://www.mediawiki.org/wiki/Extension:BugMilestone
I’ve made some additions to the last (very similar to your project) and have been in contact with the original developer. Perhaps we could start a google code project for central source and discussion, etc.
Thoughts?
Thanks.
July 16th, 2008 at 5:08 pm
Hey Ian…I owe you a beer…your nifty little Bugzilla plugin has just earned me some brownie points
I added this in yesterday but have now realised that the Bugzilla tickets are not being updated in our wiki. This isn’t browser caching. Any ideas?
Thanks!
Dean
July 16th, 2008 at 6:27 pm
Dean,
I guess you’re experiencing the MediaWiki page caching, which is in general a good thing as it improves performance for repeated access to the same page. If you want to refresh the page, hit the refresh tab (to the right of the watch tab on our wiki) which does a purge of the cache - if you don’t have a refresh tab hitting edit and save will do the same thing. If you want to change the caching strategy - take a look at http://thinkhole.org/wp/2006/09/13/disabling-caching-in-mediawiki/ or http://www.mediawiki.org/wiki/Extension:MagicNoCache (I’ve not tried out either of these, but you might find them useful).
Cheers,
Ian
July 16th, 2008 at 9:13 pm
Hi Ray,
Coordinating our efforts seems a great idea. All for it. I’m in the motions of trying to get write access to the MediaWiki SVN extensions so that I can maintain it there. It’s already been imported, but until I get write access the latest version won’t always be in that repo. Once it’s in there then I’d be on for others getting involved with it.
Cheers,
Ian
July 18th, 2008 at 3:14 pm
Thanks Ian…the tips in http://thinkhole.org/wp/2006/09/13/disabling-caching-in-mediawiki/ did the trick.
July 24th, 2008 at 1:55 pm
Really nice extension Ian,
Have you given any thought to including Original Estimate as a usable field/column? I’d *love* to be able to use the bars to make a simple burndown bar graph.
July 24th, 2008 at 2:07 pm
Yep - I just put support for reporting on estimates on my task list the other day. It’ll be coming soon … hopefully in the next release in a week or two.
August 13th, 2008 at 1:57 pm
This extension looks really cool, but I can’t get it to work.
Is there any way you’d be willing to contact me at my email address?
I’m very knowledgeable with LAMP and can’t for the life of me figure out what I’m doing wrong. I even stumped the guys in #mediawiki. If you’re willing to help, I’d really appreciate it.
August 22nd, 2008 at 9:16 am
I have this problem:
Warning: mysql_error(): supplied argument is not a valid MySQL-Link resource in /var/www/mediawiki/extensions/BugzillaReports/BMysqlConnector.php on line 46
Can you help me pls???
Thanks
August 22nd, 2008 at 2:43 pm
Hi Quentin. Yes - I spotted this bug the other day. I’ve fixed it ready for the next release. Is this preventing the report from working for you or is it only appearing in the error logs? If it is preventing the report from working for you then I’ll bring the next release forward. BTW - I tried to reply to your email you sent yesterday but the emails kept bouncing - is your email in working OK?
August 22nd, 2008 at 5:03 pm
I’ve released 0.9.3 - see http://blog.bemoko.com/bugzillareports/ - which should fix the mysql-error() regarding the MySQL-Link resource.
August 25th, 2008 at 9:16 am
Thanks a lot, I hope, that my mail is working correctly. Yes, it is preventing from workin…. It is showed on website…
Thanks a lot, I try new release.
August 26th, 2008 at 9:26 am
Hi, I have still one problem. When I use:
{{#bugzilla:
|product=test
|status=!RESOLVED
}}
I got clean page, but when I use
{{#bugzilla:
|product=test
|status=!RESOLVED
|maxrows=10
}}
It is workin, but there is about 30 bugs, which I want to display.
And
If I use
status=NEW or status=ASSIGNED or status=NEW,ASSIGNED a got clean page again.
I have mediawiki 1.13 and bugzilla 3.2rc1 both on MySQL5.
Thanks a lot
August 26th, 2008 at 11:20 pm
Would you be able to include the following in the LocalSettings.php file,
$wgDebugLogGroups = array( 'BMWExtension' => '/tmp/logs-mediawiki-BMWExtension.log' );and include debug=1 (see http://www.mediawiki.org/wiki/Extension:Bugzilla_Reports#Troubleshooting) in the bugzilla function call and send me the outputs of the logs-mediawiki-BMWExtension.log file?
BTW - I’ve not tested this extension on BZ 3.2rc1 yet - there is a chance that the issue is related to that, but hopeful the debug information would help identify whether it is.