import from bugzilla

Added by Carl Nygard over 9 years ago

Is it possible to import issues from bugzilla?

Replies (24)

RE: import from bugzilla - Added by Thomas Lecavelier over 9 years ago

At this time, only mantis and trac are supported. Maybe you want to do one? :)

Joke apart, if you can provide a bugzilla database dump (consistant, with a good set of its usage in it) someone could do it for you.

RE: import from bugzilla - Added by Carl Nygard over 9 years ago

That would be fine. I'd even be willing to work on it, at least generate the subset that "works for me". Just new to ruby so could use a skeleton, pointers, and tips.

RE: import from bugzilla - Added by Thomas Lecavelier over 9 years ago

You should have a look to the existing importer $REDMINE_ROOT/lib/tasks/migrate_from*.rb, there are not as difficult as they may look.

RE: import from bugzilla - Added by Arjen Roodselaar over 9 years ago

I reacted a basic migration task for Bugzilla last summer. I'm not sure whether it still works, but it should be a good starting point. I used it to migrate the following:

  • Bugzilla products to Redmine projects, including Bugzilla components as Redmine catagories and versions
  • Users
  • Bugs, including comments

If you want bug relations, attached files etc you'll have to implement this yourself. Good luck.

migrate_from_bugzilla.rake Magnifier - Migrate from Bugzilla (11.6 KB)

RE: RE: import from bugzilla - Added by Carl Nygard over 9 years ago

Is there a way to get Rails to save the Issue.id field when creating a new Issue? I need to preserve bug id's because we had integration with svn commit logs. So being able to keep the same id is critical to my migration scheme. Who knows how to do that?

RE: RE: RE: import from bugzilla - Added by Alejandro Celery over 9 years ago

HELP!!!!!!!!

Hi, my name is Alex, i´m from Buenos Aires, Argentina.
I just picked up Redmine as per my boss request and it seems like a hundred times better than bugzilla (which we actually use). I found this task migrate_from_bugzilla.rake and i would REALLY need to put it to good use, but i have no clue about how to do it!

This is the first time I see ruby code, so i´m quite at a loss here. Could you please point me as to how to use the task to migrate from bugzilla? Please!!!
Thanks for the time.

Regards,
Alex from Argentina

RE: import from bugzilla - Added by Thomas Lecavelier over 9 years ago

Just copy the rake file gently offered from Arjen in your $REDMINE_ROOT/lib/tasks/ directory, then run:

rake redmine:migrate_from_bugzilla RAILS_ENV="test"

to test if all went well.

Then try again with RAILS_ENV="production"

If there's problem, please report it here: we'll try to help you out of it.

Oh! A last word: crying don't make answers faster. :)

RE: RE: import from bugzilla - Added by Alejandro Celery over 9 years ago

Hi thomas, thanks for the reply.
I tried this as you said, I got only halfway through. This is the trace of the application. Can you tell what´s going wrong?

alejandro@morfeo:/var/www/redmine$ rake redmine:migrate_from_bugzilla RAILS_ENV="test" --trace
(in /var/www/redmine)
  • Invoke redmine:migrate_from_bugzilla (first_time)
  • Invoke environment (first_time)
  • Execute environment
  • Execute redmine:migrate_from_bugzilla

WARNING: Your Redmine data will be deleted during this process.
Are you sure you want to continue ? [y/N] y

Please enter settings for your Bugzilla database
adapter [mysql]:
host [localhost]:
database [bugs]: bugszilla
username [root]:
password []: **

Migrating profiles..........
Migrating products..........
rake aborted!
compile error
/usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/base.rb:1748: syntax error, unexpected tINTEGER
BugzillaMigrate::0
^
/usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/base.rb:1748:in `compute_type'
/usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/base.rb:1316:in `instantiate'
/usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/base.rb:532:in `find_by_sql'
/usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/base.rb:532:in `collect!'
/usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/base.rb:532:in `find_by_sql'
/usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/base.rb:1233:in `find_every'
/usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/base.rb:503:in `find'
/usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/associations/has_many_association.rb:66:in `find'
/usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/associations/association_collection.rb:182:in `find_target'
/usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/associations/has_many_association.rb:78:in `load_target'
/usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/associations/association_proxy.rb:124:in `method_missing'
/usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/associations/association_collection.rb:162:in `method_missing'
/var/www/redmine/lib/tasks/migrate_from_bugzilla.rake:269:in `migrate'
/var/www/redmine/lib/tasks/migrate_from_bugzilla.rake:264:in `each'
/var/www/redmine/lib/tasks/migrate_from_bugzilla.rake:264:in `migrate'
/var/www/redmine/lib/tasks/migrate_from_bugzilla.rake:345
/usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:546:in `call'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:546:in `execute'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:541:in `each'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:541:in `execute'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:508:in `invoke_with_call_chain'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:501:in `synchronize'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:501:in `invoke_with_call_chain'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:494:in `invoke'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1931:in `invoke_task'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1909:in `top_level'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1909:in `each'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1909:in `top_level'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1948:in `standard_exception_handling'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1903:in `top_level'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1881:in `run'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1948:in `standard_exception_handling'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1878:in `run'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.1/bin/rake:31
/usr/bin/rake:19:in `load'
/usr/bin/rake:19

Oh, and about

Oh! A last word: crying don't make answers faster. :)

It sure as hell makes one feel better!!!

Regards,
Alex

RE: RE: RE: import from bugzilla - Added by Carl Nygard over 9 years ago

My first suggestion would be to double check that the bugzilla version you're using matches the one he wrote it for, since the bugzilla schema changes from release to release. I'd guess your schema doesn't match his.

Go here and find your schema. Then browse through the diagram and make sure that the model laid out in the migrate script matches what you actually have.

It would help if Arjen chimed in with his bugzilla version...

--carl

RE: import from bugzilla - Added by Arjen Roodselaar over 9 years ago

I originally wrote this migration script for Bugzilla version 2.22.1. I've no idea how much has changed since so I'm afraid you're on your own here. Alex, which version of Rails are you running? I wrote this on 1.2.3 and I know there have been some changes since Rails 2.0. That might explain your error.

RE: import from bugzilla - Added by Sepp _ over 9 years ago

Hi all,

I'm impressed of redmine, so I also want to switch from bugzilla to redmine.
Now I gett the following errormessage....
Can anyone give me a hint or help me out? I can't really read/understand the sourcecode....
I would be very thankful.... My Bugzillaversion is 3.03.

Migrating profiles....................
Migrating products......
Migrating bugsrake aborted!
compile error
/opt/redmine/vendor/rails/activerecord/lib/active_record/base.rb:1748: syntax error, unexpected tINTEGER
BugzillaMigrate::0

RE: import from bugzilla - Added by Alejandro Celery over 9 years ago

Hi, thanks for the input.

I´m using Rails 2.0.2 and Bugzilla 3.0.1. I checked the BZ schemas (great tip!) and the newer version has three tables that the older one does not. I will look into this, ANY hint is appreciated.
About the rails version, what could be the problem? What should I look for IYO?

Thanks for being there.
Regards,
Alex

PS: As for the last post: sepp the problem you are reporting is the same one I have, follow up on these suggestions and let me know if you fix it!

RE: import from bugzilla - Added by Sepp _ over 9 years ago

Hello,

as I can't really understand the programmlanguage,
I'll convert my bugzilla directly using sql-statements.
At first it seems that I'll get it up and running..., and i'll need to fix the charset-table

maybe I can post more later

RE: import from bugzilla - Added by Deepak R over 9 years ago

I am trying to do this and I get this error. My bugzilla version is 2.22.3. There are no schema changes between 2.22.1 and 2.22.3. I really am not familiar with ruby. Great if someone can help. :)

I get the same kind of error with rails 2.0.2 and 1.2.6

Migrating profiles.................
Migrating products.......
rake aborted!
undefined method `trackers' for nil:NilClass
/root/redmine-0.6.4/app/models/issue.rb:110:in `validate_on_create'
/root/redmine-0.6.4/vendor/rails/activerecord/lib/active_record/validations.rb:785:in `valid_without_callbacks?'
/root/redmine-0.6.4/vendor/rails/activerecord/lib/active_record/callbacks.rb:299:in `valid?'
/root/redmine-0.6.4/vendor/rails/activerecord/lib/active_record/validations.rb:751:in `save_without_transactions'
/root/redmine-0.6.4/vendor/rails/activerecord/lib/active_record/transactions.rb:129:in `save'
/root/redmine-0.6.4/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:59:in `transaction'
/root/redmine-0.6.4/vendor/rails/activerecord/lib/active_record/transactions.rb:95:in `transaction'
/root/redmine-0.6.4/vendor/rails/activerecord/lib/active_record/transactions.rb:121:in `transaction'
/root/redmine-0.6.4/vendor/rails/activerecord/lib/active_record/transactions.rb:129:in `save'
/root/redmine-0.6.4/config/../lib/tasks/migrate_from_bugzilla.rake:281:in `migrate'
/root/redmine-0.6.4/config/../lib/tasks/migrate_from_bugzilla.rake:264:in `each'
/root/redmine-0.6.4/config/../lib/tasks/migrate_from_bugzilla.rake:264:in `migrate'
/root/redmine-0.6.4/config/../lib/tasks/migrate_from_bugzilla.rake:345
/usr/lib/ruby/1.8/rake.rb:546:in `call'
/usr/lib/ruby/1.8/rake.rb:546:in `execute'
/usr/lib/ruby/1.8/rake.rb:541:in `each'
/usr/lib/ruby/1.8/rake.rb:541:in `execute'
/usr/lib/ruby/1.8/rake.rb:508:in `invoke_with_call_chain'
/usr/lib/ruby/1.8/rake.rb:501:in `synchronize'
/usr/lib/ruby/1.8/rake.rb:501:in `invoke_with_call_chain'
/usr/lib/ruby/1.8/rake.rb:494:in `invoke'
/usr/lib/ruby/1.8/rake.rb:1931:in `invoke_task'
/usr/lib/ruby/1.8/rake.rb:1909:in `top_level'
/usr/lib/ruby/1.8/rake.rb:1909:in `each'
/usr/lib/ruby/1.8/rake.rb:1909:in `top_level'
/usr/lib/ruby/1.8/rake.rb:1948:in `standard_exception_handling'
/usr/lib/ruby/1.8/rake.rb:1903:in `top_level'
/usr/lib/ruby/1.8/rake.rb:1881:in `run'
/usr/lib/ruby/1.8/rake.rb:1948:in `standard_exception_handling'
/usr/lib/ruby/1.8/rake.rb:1878:in `run'
/usr/bin/rake:28

RE: import from bugzilla - Added by Oliver Sigge about 9 years ago

I got the same Error with Rails 2.1, Bugzilla 2.20 and the dev Build of Redmine.

I jumped into the rake task and thought there's somthing wrong with the has_and_belongs_to_many relationship and I edited the task. But that didn't help and I saw that not all of the projects from bugzilla were imported. So I fixed that. But that was not the error. I think the db schema changed in v0.7. I will continue to search for the error and report here ;)

RE: import from bugzilla - Added by Oliver Sigge about 9 years ago

I edited the rake task and now it works for me with Bugzilla 2.20, latest devBuild of Redmine and Rails 2.1. Maybe it will run on other configs, too. Feel free to test.

Please note, that the username in the Bugzilla DB must have a forename and surename. I added the encoding symbol to the db connection to bugzilla db to utf-8. You should change that, if your database got another collation.

RE: import from bugzilla - Added by Andrew Gniadek about 9 years ago

I tried out Oliver's rake task and ran into 2 issues using Rails 2.1, and Bugzilla 3.0.2:
  • A "type" column was added to bugzilla's longdescs table in bugzilla 2.23.4. ActiveRecord interprets this as the subclass to use in cases of inheritance.
  • Product names with periods should also have those escaped for the product identifier.

Here's the diff:

169a170,173
>         def self.inheritance_column
>           "inh_type" 
>         end
>         
226c230
<           project.identifier = product.name.downcase.gsub(/[0-9_\s]*/, '')[0..15]
---
>           project.identifier = product.name.downcase.gsub(/[0-9_\s\.]*/, '')[0..15]

RE: import from bugzilla - Added by Bruce Ingalls over 8 years ago

I still face a trace just like Deepak.

...
Migrating products..
rake aborted!
undefined method `trackers' for nil:NilClass
/home/bruce/redmine-0.8.0/app/models/issue.rb:127:in `validate_on_create'
...
I see a related bug in #941
My initial impression is that migrate_from_bugzilla.rake does not extend Tracker nor defines the tracker() method, unlike the other migration rake scripts.
I run
  • Bugzilla 3.0.6 (current is 3.1.4?). Off the shelf schema.
  • Redmine 0.8.0 (current)
  • Rails 2.1.2 Ruby 1.8.6 as supported by Redmine
  • FreeBSD 5.4-RELEASE

Rails requires iconv, a part of gettext. There is no documented requirement for pp, part of the Ruby gettext library, require d at the top of migrate_from_bugzilla.rake

RE: import from bugzilla - Added by Brad Beattie over 8 years ago

Carl Nygard wrote:

Is it possible to import issues from bugzilla?

There are plenty of tools out there to import from Bugzilla to Trac. From there you can do a Trac to Redmine. That should work, yeah? I know it's two-step, but it should do just fine.

ETL: extract, transform, load - Added by Bruce Ingalls over 8 years ago

Exporting Bugzilla through Trac was too painful for me.

I researched a few Free/Open ETL tools, which are designed to migrate databases. Talend Open Studio looked nice, but beyond its learning curve, it did not look easy to share its conversion script.
I attached a Scriptella [[http://scriptella.javaforge.com/]] script, which is compact and easy to read, if you know SQL.
I've only tested that it generates a sensible dump, which can be imported into a MySQL database.
For this script to be useful, it will need help from our community. Anyone familiar with Bugzilla and/or Redmine databases should be able to help.

To run this code, you must:
  • Install Scriptella into your PATH
  • Download and install your JDBC jar file into scriptella*/lib or into your CLASSPATH
  • Edit the connection parameters at the top of the attached etl.xml file. This includes ensuring /tmp exists.
  • If you are not using MySQL, then replace the call to SHA1 to an empty password
  • Ensure permissions to the empty Redmine database skeleton
  • Run scriptella
  • Run mysql -uroot -p -Dredmine < /tmp/bug2red.sql #Or equivalent

The scriptella script can be improved to avoid the last step.
The attached scriptella script works similar to migrate_from_bugzilla.rake. However, it actually ran for me. It is less powerful, and not the Ruby way, but might be easier for the community to maintain. Once the data is as good as it gets, I hope to look into updating the rakefile.

Minimal testing with
  • Scriptella 1.0rc
  • Bugzilla 3.3.3
  • Redmine 0.8

etl.xml Magnifier - Scriptella code (1.72 KB)

RE: import from bugzilla - Added by jamon camisso over 8 years ago

Bruce Ingalls wrote:

Exporting Bugzilla through Trac was too painful for me.

I've got 4-5 bugzilla databases to import into Redmine, and none will work with Trac. Your scriptella has been the most successful thusfar. I haven't had success, but I think I'm close.

I've only tested that it generates a sensible dump, which can be imported into a MySQL database.

One thing I've found is that the output for the issues table isn't quite working. The description field can contain ' and " for punctuation. I've tried altering the queries to use "" instead of '' but apostrophes etc. tend to mess up the import. Would there be any way to sanitize those via scriptella?

The attached scriptella script works similar to migrate_from_bugzilla.rake. However, it actually ran for me. It is less powerful, and not the Ruby way, but might be easier for the community to maintain. Once the data is as good as it gets, I hope to look into updating the rakefile.

I think at this point, whatever actually works, works, and is worth using.

Minimal testing with
  • Scriptella 1.0rc
  • Bugzilla 3.3.3
  • Redmine 0.8

My bugzilla instances are 3.0.5, and 2.x versions, could account for some of the problems I'm having. If I find any workarounds I'll be sure to post them here.

RE: import from bugzilla - Added by Ismael Juma over 8 years ago

I was doing some research on this and another alternative is:

http://robertheath.net/2009/02/redmine-bugzilla-migration-script/

Best,
Ismael

RE: import from bugzilla - Added by Marius Garbea over 8 years ago

I actually tried the PHP CLI script provided by Robert Heath (the link above).
It works fine. (well, there were 2 or 3 lines which I had to comment, most probably due to his conversion - his Bugzilla most certainly used custom fields).
The script is easy to understand and to modify accordint to the needs. There are long chunks of code that could be factorized as functions, but at the end of the day, this is an one-off script.
My kudos to Robert.

RE: import from bugzilla - Added by kk kk about 6 years ago

need help-
I m trying to migrate from bugzilla(3.2.5) to redmine 1.2.1 with gemlist->

  • LOCAL GEMS ***
    rack (1.1.1)
    rails (2.3.14, 2.3.11, 2.0.2)
    rake (0.9.2, 0.8.7)
    rubygems-update (1.8.10)
i tried to run the script rake redmine:migrate_from_bugzilla RAILS_ENV="test" --trace
its output

root@svn tasks]# rake redmine:migrate_from_bugzilla RAILS_ENV="test" --trace
(in /opt/redmine)
rake/rdoctask is deprecated. Use rdoc/task instead (in RDoc 2.4.2+)
WARNING: Global access to Rake DSL methods is deprecated. Please include
... Rake::DSL into classes and modules which use the Rake DSL methods.
WARNING: DSL method Module#namespace called at /opt/redmine/lib/tasks/migrate_fr
WARNING: DSL method Module#task called at /opt/redmine/lib/tasks/migrate_from_bu
  • Invoke redmine:migrate_from_bugzilla (first_time)
  • Invoke environment (first_time)
  • Execute environment
  • Execute redmine:migrate_from_bugzilla

WARNING: Your Redmine data could be corrupted during this process.
Are you sure you want to continue ? [y/N] y

Please enter settings for your Bugzilla database
Migrating profiles...
Migrating products....
Migrating Issues.....\
****First time it ran fine, but took lot of time & had to hang it after 8 hrs when it was here.

it did showed things properly but custom fields were not coming & had some numbering issue. so i thought to restart it.
but is started with same cmd- it gave error>
Migrating productsrake aborted!
Validation failed: Identifier has already been taken
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.11/lib/active_record/validations.rb:1102:in `save_without_dirty!'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.11/lib/active_record/dirty.rb:87:in `save_without_transactions!'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.11/lib/active_record/transactions.rb:200:in `save!'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.11/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in `transaction'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.11/lib/active_record/transactions.rb:182:in `transaction'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.11/lib/active_record/transactions.rb:200:in `save!'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.11/lib/active_record/transactions.rb:208:in `rollback_active_record_state!'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.11/lib/active_record/transactions.rb:200:in `save!'
/opt/redmine/lib/tasks/migrate_from_bugzilla.rake:311:in `migrate_products'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.11/lib/active_record/batches.rb:26:in `find_each'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.11/lib/active_record/batches.rb:26:in `each'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.11/lib/active_record/batches.rb:26:in `find_each'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.11/lib/active_record/batches.rb:66:in `find_in_batches'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.11/lib/active_record/batches.rb:25:in `find_each'
/opt/redmine/lib/tasks/migrate_from_bugzilla.rake:306:in `migrate_products'
/opt/redmine/lib/tasks/migrate_from_bugzilla.rake:509
/usr/local/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:205:in `call'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:205:in `execute'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:200:in `each'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:200:in `execute'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:158:in `invoke_with_call_chain'
/usr/local/lib/ruby/1.8/monitor.rb:242:in `synchronize'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:151:in `invoke_with_call_chain'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:144:in `invoke'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:112:in `invoke_task'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:90:in `top_level'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:90:in `each'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:90:in `top_level'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:129:in `standard_exception_handling'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:84:in `top_level'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:62:in `run'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:129:in `standard_exception_handling'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:59:in `run'
/usr/local/lib/ruby/gems/1.8/gems/rake-0.9.2/bin/rake:32
/usr/local/bin/rake:19:in `load'
/usr/local/bin/rake:19
Tasks: TOP => redmine:migrate_from_bugzilla

Unable to start the script, do u need to drop mysql table & reconstruct it?? or what i m doing wrong?
+ i m new to ruby, so what does this test run & production run has a difference? i am able to see the changes in redmine.

any help is appreciated.

(1-24/24)