software-project / scrum-pm

Scrum PM is a plugin for Redmine ticket management system. It adds Scrum items like backlog, dashboard and others.
www.software-project.eu/EN/scrumpm
126 stars 47 forks source link

Click on Dashboard tab gives "Internal error" page #31

Closed jmaynier closed 14 years ago

jmaynier commented 14 years ago

After installing scrum-pm and activating the sprint module for a project, when I click on the Dashboard tab I get the redmine error page :

"Internal error

An error occurred on the page you were trying to access. If you continue to experience problems please contact your redMine administrator for assistance."

In the log I have :

"Processing SprintsController#show (for 82.247.13.79 at 2010-04-26 11:32:29) [GET] Parameters: {"project_id"=>"eco2data", "action"=>"show", "id"=>"show", "controller"=>"sprints"}

ActiveRecord::StatementInvalid (PGError: ERROR: operator does not exist: integer = boolean HINT: No operator matches the given name and argument type(s). You may need to add explicit type casts. : SELECT * FROM "issues" WHERE (user_story_id IS NULL AND (fixed_version_id = 3 || project_id = 3)) ): vendor/plugins/redmine_sprints/app/controllers/sprints_controller.rb:30:in show' /opt/passenger-2.2.9/lib/phusion_passenger/rack/request_handler.rb:92:inprocess_request' /opt/passenger-2.2.9/lib/phusion_passenger/abstract_request_handler.rb:207:in main_loop' /opt/passenger-2.2.9/lib/phusion_passenger/railz/application_spawner.rb:400:instart_request_handler' /opt/passenger-2.2.9/lib/phusion_passenger/railz/application_spawner.rb:351:in handle_spawn_application' /opt/passenger-2.2.9/lib/phusion_passenger/utils.rb:184:insafe_fork' /opt/passenger-2.2.9/lib/phusion_passenger/railz/application_spawner.rb:349:in handle_spawn_application' /opt/passenger-2.2.9/lib/phusion_passenger/abstract_server.rb:352:insend' /opt/passenger-2.2.9/lib/phusion_passenger/abstract_server.rb:352:in main_loop' /opt/passenger-2.2.9/lib/phusion_passenger/abstract_server.rb:196:instart_synchronously' /opt/passenger-2.2.9/lib/phusion_passenger/abstract_server.rb:163:in start' /opt/passenger-2.2.9/lib/phusion_passenger/railz/application_spawner.rb:209:instart' /opt/passenger-2.2.9/lib/phusion_passenger/spawn_manager.rb:262:in spawn_rails_application' /opt/passenger-2.2.9/lib/phusion_passenger/abstract_server_collection.rb:126:inlookup_or_add' /opt/passenger-2.2.9/lib/phusion_passenger/spawn_manager.rb:256:in spawn_rails_application' /opt/passenger-2.2.9/lib/phusion_passenger/abstract_server_collection.rb:80:insynchronize' /opt/passenger-2.2.9/lib/phusion_passenger/abstract_server_collection.rb:79:in synchronize' /opt/passenger-2.2.9/lib/phusion_passenger/spawn_manager.rb:255:inspawn_rails_application' /opt/passenger-2.2.9/lib/phusion_passenger/spawn_manager.rb:154:in spawn_application' /opt/passenger-2.2.9/lib/phusion_passenger/spawn_manager.rb:287:inhandle_spawn_application' /opt/passenger-2.2.9/lib/phusion_passenger/abstract_server.rb:352:in __send__' /opt/passenger-2.2.9/lib/phusion_passenger/abstract_server.rb:352:inmain_loop' /opt/passenger-2.2.9/lib/phusion_passenger/abstract_server.rb:196:in `start_synchronously'

Rendering /opt/redmine/public/500.html (500 Internal Server Error) " I use Redmine v0.9.3 with Postgres and the following plugins installed : action_mailer_optional_tls acts_as_versioned gravatar acts_as_activity_provider acts_as_watchable open_id_authentication acts_as_attachable attachment_fu prepend_engine_views acts_as_customizable awesome_nested_set redmine_hudson acts_as_event classic_pagination redmine_sprints acts_as_list coderay-0.7.6.227 rfpdf acts_as_searchable engines ruby-net-ldap-0.0.4 acts_as_tree google_analytics_plugin

The Backlog tab works well.

jbye commented 14 years ago

I get the same error with a clean install of redmine trunk and the scrum-pm plugin. As with the above poster the Backlog tab works.

I've also got a question. I've made several backlog entries and assigned some of them to a sprint. Should these show up in the roadmap? I haven't really found much documentation on the use of this plugin, and I haven't figured out how the status of the stories are set (to done, for example). I am however guessing that is done in the Dashboard :-)

I've added the dump from my production log as well:

Processing SprintsController#show (for xxx.xxx.xxx.xxx at 2010-05-03 12:11:43) [GET] Parameters: {"project_id"=>"test", "action"=>"show", "id"=>"show", "controller"=>"sprints"}

ActiveRecord::StatementInvalid (PGError: ERROR: operator does not exist: boolean = integer LINE 1: ...ssues".status_id WHERE (issue_statuses.is_closed = 0 AND us... ^ HINT: No operator matches the given name and argument type(s). You might need to add explicit type casts. : SELECT "issues".* FROM "issues" INNER JOIN "issue_statuses" ON "issue_statuses".id = "issues".status_id WHERE (issue_statuses.is_closed = 0 AND user_story_id IS NULL AND (fixed_version_id = 1 OR project_id = 1)) ): vendor/plugins/redmine_sprints/app/controllers/sprints_controller.rb:30:in show' /usr/lib/ruby/1.8/phusion_passenger/rack/request_handler.rb:92:inprocess_request' /usr/lib/ruby/1.8/phusion_passenger/abstract_request_handler.rb:207:in main_loop' /usr/lib/ruby/1.8/phusion_passenger/railz/application_spawner.rb:400:instart_request_handler' /usr/lib/ruby/1.8/phusion_passenger/railz/application_spawner.rb:351:in handle_spawn_application' /usr/lib/ruby/1.8/phusion_passenger/utils.rb:184:insafe_fork' /usr/lib/ruby/1.8/phusion_passenger/railz/application_spawner.rb:349:in handle_spawn_application' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:insend' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:in main_loop' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:196:instart_synchronously' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:163:in start' /usr/lib/ruby/1.8/phusion_passenger/railz/application_spawner.rb:209:instart' /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:262:in spawn_rails_application' /usr/lib/ruby/1.8/phusion_passenger/abstract_server_collection.rb:126:inlookup_or_add' /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:256:in spawn_rails_application' /usr/lib/ruby/1.8/phusion_passenger/abstract_server_collection.rb:80:insynchronize' /usr/lib/ruby/1.8/phusion_passenger/abstract_server_collection.rb:79:in synchronize' /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:255:inspawn_rails_application' /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:154:in spawn_application' /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:287:inhandle_spawn_application' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:in __send__' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:inmain_loop' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:196:in `start_synchronously' /usr/lib/phusion_passenger/passenger-spawn-server:61

Rendering /opt/redmine_upbeat/public/500.html (500 Internal Server Error)

jbye commented 14 years ago

I forgot to mention that I am using the postgresql adapter

jbye commented 14 years ago

This issue has been solved for me by doing a git pull ten minutes ago. :-)

I'm however wondering if it's normal that:

  1. If I add a task via the Dashboard, I need to refresh the page to see it.
  2. If I drag a task to lets say, Done, I am sent to the Issue Page (/show/id). If I go back to the dashboard the task is correctly placed in the Done column and is colored green.
KuzminStepan commented 14 years ago

I have got a similar error. After installing plugin I have "500 Internal server error" trying to access to Backlog or Dashboard.