Problem migrating database from bugzilla 2.20.2 to bugzilla 3.0
I installed bugzilla 3.0 and was working fine till I tried migrating
the mysql db from previous version of bugzilla 2.20.2. These two
versions are on different machines. I created .dmp file to get the
data in bugzilla 2.20.2 to update it to bugzilla 3.0. Tables seemed to
be updated(not sure if there is mismatch between the table structure),
but after that upon trying to run checksetup.pl script, I am getting
the following message
"There was an error connecting to MySQL:
Access denied for user 'bugs'@'localh...Issue With Migrating Bugzilla 3.0.5 to Bugzilla 4.0.2
ERROR: There are invalid values for the assigned_to column in the bugs
table. (These values do not exist in the profiles table, in the userid
column.) Before continuing with checksetup, you will need to fix these
values, either by deleting these rows from the database, or changing
the values of assigned_to in bugs to point to valid values in
profiles.userid. The bad values from the bugs.assigned_to column are:
13, 16, 22, 23, 38, 40
On 01/12/11 11:33, Krishnaraj B wrote:
> ERROR: There are invalid values for the assigned_to column in the bugs
> table. (These values do not exist...Migrating Bugzilla 2.20 to Bugzilla 3
I'm new in the list but I'd like to say how such a good work you have
done on this version of Bugzilla.
I'm using bugzilla 2.20 but tried to upgrade it to bugzilla 3 but
unfortunately just export the database of Bugzilla 2.20 to Bugzilla 3
database didn't worked.
I'm looking for at web but I've get any result yet.
Leonardo A. M. dos Santos
HST Sistemas & Tecnologia
Service Desk - Fábrica de Softwares
Fone: +55 19 3294-0331
...Security Advisory for Bugzilla 3.0.3, 3.1.3, 2.22.3, and 2.20.5
Content-Type: text/plain; charset=UTF-8
Bugzilla is a Web-based bug-tracking system, used by a large number of
This advisory covers three security issues that have recently been
fixed in the Bugzilla code:
* Users without the "canconfirm" privilege could enter a bug as NEW
or ASSIGNED by using the XML-RPC interface.
* When viewing several bugs at once, there was a Cross-Site Scripting
* The inbound email interface allowed you t...Migrating the Bugzilla database from 2.20.5 to 3.1.3
Hello; I have been searching for a utility, Perl script, etc., to assist
in migrating the Bugzilla database from 2.20.5 to 3.1.3.=20
Will move.pl work for this? Do I need to CVS?=20
Any help will be appreciated,=20
On 6/24/2008 11:41 AM, Grant, Bruce J wrote:
> Hello; I have been searching for a utility, Perl script, etc., to assist
> in migrating the Bugzilla database from 2.20.5 to 3.1.3.
That's what checksetup.pl is for.
...upgrade bugzilla and migrate database from 2.16.3 to 2.20
i tried to migrate our bugzilla installation (suse linux) from version
2.16.3 to 2.20. I used the CVS upgrade and it seemed to work perfect. The
check checksetup.pl script dedected errors in the database (mysql). Droping
the database and running the checksetup spript worked fine, but I want to
migrate the existing database to version 2.20. I did not find any HOWTO.
Can anybody help?
regards Thomas Mayer
Thomas Mayer wrote:
> i tried to migrate our bugzilla installation (suse linux) from version
> 2.16.3 to 2.20. I used the CVS upgrade and it seemed to ...P4DTI 2.3.0 released to support Bugzilla 2.20
I have made release 2.3.0 of the Perforce Defect Tracking Integration
This release works with Bugzilla 2.20 and with Perforce servers in
Unicode mode, and the User's Guide includes instructions for P4V
This release has not yet been approved by Perforce Inc. As and when
it is approved, it will be uploaded to the Perforce public repository.
Unless and until it is approved, it is not a supported product of
In the meantime, I welcome feedback from anyone prepared to try this
release...RE:upgrade bugzilla and migrate database from 2.16.3 to 2.20
We are trying to do the same thing.
I tried this from another post:
have migrated my *Bugzilla **2.16* to *Bugzilla* 2.19.2 as follow:
- on the *2.16* -> % mysqldump -u root -p --opt --all bugs > bugs.sql
- copy the bugs.sql to the new server (2.18)
- rename bugs on the new server (2.18)
- % mysqladmin create bugs
- % mysql bugs < bugs.sql
- % mysqladmin flush-privileges
- % ./checksetup.pl
- % ./collectstats.pl
bug the checksetup.pl script errored out and gives me this message
DBD::mysql::st execute failed: Unknown column 'groups.id' in 'field
list'...Testopia 1.3 (Bugzilla 3.0) and Testopia 1.2.2 (Bugzilla 2.22.x) Released
Testopia 1.3 has been released.=20
This Testopia is compatible with Bugzilla 3.0 and mod_perl and provides
For those of you still running Bugzilla 2.22.x, I am also releasing
1.2.2 which is a (major) bug fix release.
They are available from the project home page at
Thanks for all the feedback. Keep it coming.
...[ANN] Release of Bugzilla 3.0.1, 3.1.1, 2.22.3, and 2.20.5
Content-Type: text/plain; charset=US-ASCII
Today the Bugzilla project has four releases!
3.0.1 is the first bug-fix release for the 3.0 series. 3.0 was very
stable, but 3.0.1 adds a lot of little polish fixes that greatly improve
the experience of using Bugzilla.
3.1.1 is our first development release toward Bugzilla 3.2. It has
a huge number of new features, but is EXTREMELY UNSTABLE. It has not
been tested, and should not be used in a production environment. It may
fail in critical ways, or destro...[ANN] Release of Bugzilla 3.2.2, 3.0.8, and 3.3.3
Bugzilla 3.2.1, 3.0.7, and 3.3.2 contained a bug that was critical
for any installation running under mod_perl, due to an unintentional
interaction between the various security fixes in those releases. We
are releasing three new releases today to fix the critical issue:
3.2.2, 3.0.8, and 3.3.3. They are identical to the previous release
except that they have this one fix for installations running under
Bugzilla is available at:
Details of the fix are in the Security Adviso...[ANN] Release of Bugzilla 3.2.1, 3.0.7, 2.22.7, and 3.3.2
Today we have some major security improvements for Bugzilla in the
form of four releases. We strongly recommend that all Bugzilla
administrators read the Security Advisory for these releases, which is
linked below in this email.
Bugzilla 3.2.1 is our latest stable release. It contains various
useful bug fixes in addition to major security improvements.
Bugzilla 3.0.7 and Bugzilla 2.22.7 are security updates for their
Bugzilla 3.3.2 is an unstable development release. In addition to the
security fixes that all the other releases contain, this release
contains n...[ANN] Release of Bugzilla 3.0.4, 3.1.4, 2.22.4, and 2.20.6
Content-Type: text/plain; charset=US-ASCII
The Bugzilla project has four releases today!
Bugzilla 3.0.4 is the latest stable version of Bugzilla, containing
several useful bug fixes over 3.0.3, particularly for the inbound email
Bugzilla 3.1.4 is our latest unstable development preview. It should
be more stable than 3.1.3, though we still don't recommend it for
production environments. Provided we don't find too many major issues
in this release, our next release will be Bugzilla...Bugzilla Upgrade
Hi Support Team,
I plan to upgrade from Bugzilla 3.0.3 to 3.2.2 .
Our bugzilla setup has a lot of "Custom fileds" .=20
I went thro' the upgrade notes but that does not explicitly=20
mention about the steps that I need to follow with "Custom Fields".=20
Do I need to copy some files from template/en/custom to the new location
Please let me know the steps that I need to follow for the upgrade with
Thanks for your help!