Defect #48

Regression: Admin raises issue in project not assigned to

Added by Jeffrey Jones almost 14 years ago. Updated almost 14 years ago.

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

0%

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

Description

I am pretty sure I saw a note somewhere that this had been fixed once. Now if an admin tries to raise an issue in a
project not assigned to the following error is displayed.

You have a nil object when you didn't expect it!
You might have expected an instance of Array.
The error occurred while evaluating nil.sort

#{RAILS_ROOT}/app/models/issue_status.rb:51:in `find_new_statuses_allowed_to'
#{RAILS_ROOT}/app/controllers/projects_controller.rb:219:in `add_issue'
-e:3:in `load'
-e:3

I believe this is caused by the recent workflow changes.

History

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

Oops, it was not really fixed. Now it should be.

#2 Updated by Jean-Philippe Lang almost 14 years ago

You're right. Fixed.
Thanks

Also available in: Atom PDF