Moving an issue to a project without same tracker results in 505
Replies (3)
RE: Moving an issue to a project without same tracker results in 505
-
Added by Felix Schäfer about 14 years ago
See if you can reproduce in on the demo redmine and open a new bug if you can (provided you have already searched that it hasn't been reported already).
RE: Moving an issue to a project without same tracker results in 505
-
Added by Mischa The Evil about 14 years ago
Simon Z wrote:
When I move an issue with tracker Bug to a project not having the Bug tracker it results in a 505 page.
Has anyone experienced this behavior or might it be our setup?
I've tried to reproduce this error but it seems I'm not able to using a checkout of the trunk at r4425.
Instead, I receive a flash-error notice about the impossibility of the move action (which is what I expected):
RE: Moving an issue to a project without same tracker results in 505
-
Added by Simon Z about 14 years ago
I couldn't reproduce it on the redmine demo site so I guess it is something with the plugins.
This is the error I get.
Processing IssueMovesController#create (for 10.6.17.115 at 2010-11-24 10:47:48) [POST]
Parameters: {"start_date"=>"", "new_tracker_id"=>"", "commit"=>"Flytta", "ids"=>["8705"], "new_project_id"=>"202", "action"=>"create", "authenticity_token"=>"VctMCM1kjgLyfpO4FW0xvRtU4PVJL0+TODkdbLLgffQ=", "assigned_to_id"=>"", "due_date"=>"", "controller"=>"issue_moves", "status_id"=>""}
NoMethodError (undefined method `project_id' for false:FalseClass):
app/models/issue.rb:106:in `move_to_project'
app/models/issue.rb:105:in `move_to_project'
app/controllers/issue_moves_controller.rb:22:in `create'
app/controllers/issue_moves_controller.rb:18:in `each'
app/controllers/issue_moves_controller.rb:18:in `create'
Rendering e:/redmine/public/500.html (500 Internal Server Error)