Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
BugzillaMetrics1_3.zip | 2014-01-05 | 16.2 MB | |
readme.txt | 2013-12-28 | 1.6 kB | |
Totals: 2 Items | 16.2 MB | 0 |
BugzillaMetrics Version 1.3 supports Bugzilla version 2.19.3 up to at least 4.4. Changes in release 1.3 ======================= Bugfix for evaluations on "keywords" in Bugzilla version >= 4 Upgrade to GWT 2.5.1 Using the new Status workflow of Bugzilla 4.0 ============================================= A new status workflow was introduced in Bugzilla 4.0. You can decide whether to use your Bugzilla with the old or the new status workflow. Both workflows are supported by BugzillaMetrics. Plese see section 5.1.1 of the documentation on how to setup the metrics depending on the used workflow. Updating BugzillaMetrics from version 1.0 or earlier ==================================================== Do the following changes in your "settings.xml" file: Change the attribute "coreConfiguration" of the element "<calculationCore>" to: coreConfiguration="org.qmetric.bugzilla.CoreConfigurationBugzilla" Change the attribute "dataProvider" of the element "<frontend>" to: dataProvider="org.qmetric.frontend.server.dataProvider.bugzilla.DataProviderForBugzilla" Updating BugzillaMetrics from version 0.9.8.1 or earlier ======================================================== Run the script "http://bugzillametrics.org/ReleaseNotes/update_bugzillametrics.sql" on your BugzillaMetrics database. If your Bugzilla database contains more than 20.000 issues, make sure that the max_allowed_packet setting of MySQL is at least 16MB. This setting can be changed in the configuration file /etc/my.cnf (See http://dev.mysql.com/doc/refman/6.0/en/program-variables.html)