![]() var/www/redmine/lib/tasks/migrate_from_bugzilla.rake:345 ![]() var/www/redmine/lib/tasks/migrate_from_bugzilla.rake:264:in `each' var/www/redmine/lib/tasks/migrate_from_bugzilla.rake:269:in `migrate' usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/associations/association_collection.rb:162:in `method_missing' 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/has_many_association.rb:78:in `load_target' 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:66:in `find' ![]() 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:1748: syntax error, unexpected tINTEGER Please enter settings for your Bugzilla database WARNING: Your Redmine data will be deleted during this process.Īre you sure you want to continue ? y Invoke redmine:migrate_from_bugzilla (first_time).Can you tell what´s going rake redmine:migrate_from_bugzilla RAILS_ENV="test" -trace If you don’t know how to do this, see the instructions below.I tried this as you said, I got only halfway through. Add a custom field in Bugzilla, named cf_pt_id (Type is ‘ Free Text‘).In Extension.pm, update the CONFIG_API_TOKEN constant (line 33).Change the directory’s name to “PractiTest”.Copy this folder to the ‘ Extensions‘ directory of Bugzilla.Install extra perl modules: REST::Client, JSON, Digest::MD5, Crypt::SSLeay, Data::Dumper (via cpan).Adding the designated Bugzilla Extention for PractiTest. To configure the two-way integration follow these steps:ġ. This document describes how the two-way integration works and how to set it up.Ĭonfiguring and working with the two-way Integration ![]() Updated: PractiTest allows you to set different projects to open directly in Bugzilla – See Two-Way integration – works like the one-way integration, but in addition, displays in PractiTest the bug’s subject and status as it appears in Bugzilla, and also allows Bugzilla to update PractiTest (via a dedicated plugin) whenever the subject or status are modified.Once you click on the Fail & Issue link in a test run, it will open a new bug form in Bugzilla, with all the data (steps and actual results) already pre-entered inside Bugzilla. One-Way integration – standard integration that works like all other PractiTest integrations.PractiTest has two types of issue integration with Bugzilla:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |