Defect #75

500 error when creating an issue with no default status selected

Added by Rob Sterner almost 12 years ago. Updated almost 12 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Resolution: Affected version:

Description

The top of the stack trace:

Processing ProjectsController#add_issue (for XXX.XXX.XXX.XXX at 2007-07-10 13:38:57) [GET]
Session ID: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Parameters: {"action"=>"add_issue", "id"=>"1",
"controller"=>"projects", "tracker_id"=>"2"}

NoMethodError (undefined method `find_new_statuses_allowed_to' for nil:NilClass):
/app/controllers/projects_controller.rb:219:in `add_issue'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/base.rb:1095:in `send'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/base.rb:1095:in
`perform_action_without_filters'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/filters.rb:632:in `call_filter'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/filters.rb:634:in `call_filter'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/filters.rb:638:in `call_filter'

Adding a default status fixed it, but this shouldn't cause a 500 error. It's a minor bug, but it's an annoying one :-D

History

#1 Updated by Jean-Philippe Lang almost 12 years ago

Hi,
This problem was fixed in rev 560 (after 0.5 release).
A proper error message is now displayed instead of a 500 error.

Regards

Also available in: Atom PDF