Forums » Problems or support »
【Need Help】Scrum 0.7.0 Usage Issue---Important FOR fixing(Redmine Calendar can not display)
Added by an li almost 10 years ago
Description:¶
For I have installed many plug-ins, for testing which plug-in leads this error, I remove all plug-ins and put it back one by one to test which is the main reason for the error, when I put scrum 0.7.0 into, this error reproduces.
When I remove scrum 0.7 from the plug-in direcotry, other plug-ins are remained in the directory. Redmine calendar is working well.
So I think it is a hiding bug in scrum 0.7, For scrum 0.8 cannot be ueds normally now(I have posted the issues in other article), and our project is using scrum 0.7, It is really urgent issue, can you help to fix scrum 0.7's bug?
Thanks very much!
////////////////////////////////////////////////////
production.log¶
An error occurred while executing the query and has been logged. Please report this error to your Redmine administrator.
Started GET "/redmine/projects/xxx/issues/calendar" for xxat 2014-11-17 14:35:31 +0800 Processing by CalendarsController#show as HTML Parameters: {"project_id"=>"xx} Current user: xx(id=28) Creating scope :system. Overwriting existing method Enumeration.system. Query::StatementInvalid: Mysql2::Error: Column 'start_date' in where clause is ambiguous: SELECT `issues`.`id` AS t0_r0, `issues`.`tracker_id` AS t0_r1, `issues`.`project_id` AS t0_r2, `issues`.`subject` AS t0_r3, `issues`.`description` AS t0_r4, `issues`.`due_date` AS t0_r5, `issues`.`category_id` AS t0_r6, `issues`.`status_id` AS t0_r7, `issues`.`assigned_to_id` AS t0_r8, `issues`.`priority_id` AS t0_r9, `issues`.`fixed_version_id` AS t0_r10, `issues`.`author_id` AS t0_r11, `issues`.`lock_version` AS t0_r12, `issues`.`created_on` AS t0_r13, `issues`.`updated_on` AS t0_r14, `issues`.`start_date` AS t0_r15, `issues`.`done_ratio` AS t0_r16, `issues`.`estimated_hours` AS t0_r17, `issues`.`parent_id` AS t0_r18, `issues`.`root_id` AS t0_r19, `issues`.`lft` AS t0_r20, `issues`.`rgt` AS t0_r21, `issues`.`is_private` AS t0_r22, `issues`.`closed_on` AS t0_r23, `issues`.`sprint_id` AS t0_r24, `issues`.`position` AS t0_r25, `projects`.`id` AS t1_r0, `projects`.`name` AS t1_r1, `projects`.`description` AS t1_r2, `projects`.`homepage` AS t1_r3, `projects`.`is_public` AS t1_r4, `projects`.`parent_id` AS t1_r5, `projects`.`created_on` AS t1_r6, `projects`.`updated_on` AS t1_r7, `projects`.`identifier` AS t1_r8, `projects`.`status` AS t1_r9, `projects`.`lft` AS t1_r10, `projects`.`rgt` AS t1_r11, `projects`.`inherit_members` AS t1_r12, `projects`.`product_backlog_id` AS t1_r13, `projects`.`enforce_issue_id` AS t1_r14, `issue_statuses`.`id` AS t2_r0, `issue_statuses`.`name` AS t2_r1, `issue_statuses`.`is_closed` AS t2_r2, `issue_statuses`.`is_default` AS t2_r3, `issue_statuses`.`position` AS t2_r4, `issue_statuses`.`default_done_ratio` AS t2_r5, `trackers`.`id` AS t3_r0, `trackers`.`name` AS t3_r1, `trackers`.`is_in_chlog` AS t3_r2, `trackers`.`position` AS t3_r3, `trackers`.`is_in_roadmap` AS t3_r4, `trackers`.`fields_bits` AS t3_r5, `users`.`id` AS t4_r0, `users`.`login` AS t4_r1, `users`.`hashed_password` AS t4_r2, `users`.`firstname` AS t4_r3, `users`.`lastname` AS t4_r4, `users`.`mail` AS t4_r5, `users`.`admin` AS t4_r6, `users`.`status` AS t4_r7, `users`.`last_login_on` AS t4_r8, `users`.`language` AS t4_r9, `users`.`auth_source_id` AS t4_r10, `users`.`created_on` AS t4_r11, `users`.`updated_on` AS t4_r12, `users`.`type` AS t4_r13, `users`.`identity_url` AS t4_r14, `users`.`mail_notification` AS t4_r15, `users`.`salt` AS t4_r16, `users`.`apps` AS t4_r17, `enumerations`.`id` AS t5_r0, `enumerations`.`name` AS t5_r1, `enumerations`.`position` AS t5_r2, `enumerations`.`is_default` AS t5_r3, `enumerations`.`type` AS t5_r4, `enumerations`.`active` AS t5_r5, `enumerations`.`project_id` AS t5_r6, `enumerations`.`parent_id` AS t5_r7, `enumerations`.`position_name` AS t5_r8, `sprints`.`id` AS t6_r0, `sprints`.`name` AS t6_r1, `sprints`.`description` AS t6_r2, `sprints`.`start_date` AS t6_r3, `sprints`.`end_date` AS t6_r4, `sprints`.`user_id` AS t6_r5, `sprints`.`project_id` AS t6_r6, `sprints`.`created_on` AS t6_r7, `sprints`.`updated_on` AS t6_r8, `sprints`.`is_product_backlog` AS t6_r9 FROM `issues` LEFT OUTER JOIN `projects` ON `projects`.`id` = `issues`.`project_id` LEFT OUTER JOIN `issue_statuses` ON `issue_statuses`.`id` = `issues`.`status_id` LEFT OUTER JOIN `trackers` ON `trackers`.`id` = `issues`.`tracker_id` LEFT OUTER JOIN `users` ON `users`.`id` = `issues`.`assigned_to_id` LEFT OUTER JOIN `enumerations` ON `enumerations`.`id` = `issues`.`priority_id` AND `enumerations`.`type` IN ('IssuePriority') LEFT OUTER JOIN `sprints` ON `sprints`.`id` = `issues`.`sprint_id` WHERE (((projects.status <> 9 AND projects.id IN (SELECT em.project_id FROM enabled_modules em WHERE em.name='issue_tracking')) AND ((projects.id IN (30) AND ((issues.is_private = 0 OR issues.author_id = 28 OR issues.assigned_to_id IN (28,24,69,239)))) OR (projects.id IN (30) AND ((issues.is_private = 0 OR issues.author_id = 28 OR issues.assigned_to_id IN (28,24,69,239)))) OR (projects.id IN (26) AND ((issues.is_private = 0 OR issues.author_id = 28 OR issues.assigned_to_id IN (28,24,69,239))))))) AND (((start_date BETWEEN '2014-10-26' AND '2014-12-06') OR (due_date BETWEEN '2014-10-26' AND '2014-12-06'))) AND ((issues.status_id IN (SELECT id FROM issue_statuses WHERE is_closed=0)) AND projects.id = 30) Rendered common/error.html.erb within layouts/base (0.0ms) Rendered plugins/redmine__select2/app/views/redmine__select2/_includes.html.erb (0.0ms) Rendered plugins/redmine_code_review/app/views/code_review/_html_header.html.erb (0.0ms) Rendered plugins/redmine_create_wiki_page/app/views/create_wiki_page/_init_create_wiki_page.erb (0.0ms) Rendered inline template (15.6ms) Rendered plugins/scrum/app/views/scrum_hooks/_head.html.erb (0.0ms) Rendered plugins/clipboard_image_paste/app/views/clipboard_image_paste/_headers.html.erb (0.0ms) Rendered plugins/redmine_simple/app/views/hooks/redmine_simple/_includes.html.erb (0.0ms) Starting Application Space plugin for Redmine Rendered plugins/progressive_projects_list/app/views/application/_progressive_sidebar.html.erb (0.0ms) Creating scope :sorted. Overwriting existing method User.sorted. Rendered plugins/progressive_projects_list/app/views/application/_progressive_recent_projects.html.erb (0.0ms) Rendered plugins/redmine_banner/app/views/banner/_project_body_bottom.html.erb (0.0ms) Rendered plugins/sidebar_hide/app/views/sidebar/_hideButton_partial.html.erb (15.6ms) Rendered plugins/redmine_banner/app/views/banner/_body_bottom.html.erb (0.0ms) Rendered plugins/redmine_banner/app/views/banner/_after_top_menu.html.erb (0.0ms) Rendered plugins/redmine_code_review/app/views/code_review/_body_bottom.html.erb (0.0ms) Rendered plugins/clipboard_image_paste/app/views/clipboard_image_paste/_add_form.html.erb (0.0ms) Completed 500 Internal Server Error in 796ms (Views: 421.2ms | ActiveRecord: 93.6ms)
Replies (9)
RE: 【Need Help】Scrum 0.7.0 Usage Issue---Important FOR fixing(Redmine Calendar can not display) - Added by an li almost 10 years ago
I submit #90 defect.
RE: 【Need Help】Scrum 0.7.0 Usage Issue---Important FOR fixing(Redmine Calendar can not display) - Added by Cori Hsu over 9 years ago
Hi ! Please reference below ..... _
http://stackoverflow.com/questions/22967037/redmine-calendar-view-not-working
(1) vi [redmine_root_path]/app/controllers/calendars_controller.rb
(2) change "start_date" to "issues.start_date"
(3) restart your redmine
RE: 【Need Help】Scrum 0.7.0 Usage Issue---Important FOR fixing(Redmine Calendar can not display) - Added by Stanislas Dourdin over 9 years ago
I think it is better to not modify the Redmine code, but rather the plugin's code as I suggested here : https://redmine.ociotec.com/issues/847#note-4
RE: 【Need Help】Scrum 0.7.0 Usage Issue---Important FOR fixing(Redmine Calendar can not display) - Added by an li over 9 years ago
Thanks so much, I have followed your solution, change database field about sprint start date and end date, then replace all "start date, end date" with new name in all plugin's code files, 7 files needs to update:
\htdocs\plugins\scrum\app\controllers\sprints_controller.rb
\htdocs\plugins\scrum\app\models\sprint.rb
\htdocs\plugins\scrum\app\views\post_its\sprint_board\_head.html.erb
\htdocs\plugins\scrum\app\views\projects\settings\_sprints.html.erb
\htdocs\plugins\scrum\app\views\sprints\_form.html.erb
\htdocs\plugins\scrum\app\views\sprints\edit_effort.html.erb
\htdocs\plugins\scrum\lib\scrum\project_patch.rb (2 hits)
then migrate the database and restart redmine, calendar can be available!
RE: 【Need Help】Scrum 0.7.0 Usage Issue---Important FOR fixing(Redmine Calendar can not display) - Added by an li over 9 years ago
About scrum 0.7.x other issues and 0.8 issues I submit days before, if you have time to fix, it will be very nice of your work, we are applying scrum a few months, really helps us, apperiate your effort!!
RE: 【Need Help】Scrum 0.7.0 Usage Issue---Important FOR fixing(Redmine Calendar can not display) - Added by Stanislas Dourdin over 9 years ago
Glad you are happy :)
More important than your calendar, does your Scrum still works ? :)
I am pretty new to Redmine and first time with Scrum, but I can try to have a look to your issues.
Regards.
RE: 【Need Help】Scrum 0.7.0 Usage Issue---Important FOR fixing(Redmine Calendar can not display) - Added by an li over 9 years ago
All issues I submit:
- 928 Sprint burndown chart not reflect wanted burndown chart drawed by manually
- 927 Sprint burndown chart pending effort is using done effort data
- 924 Burn down chart data display
- 904 sprint board task move does not be restricted by redmine default issue flow
- 903 start date and due date are shown as list or blank
- 902 Created user story not display in sprint board and backlog
- 901 Product backlog has repeated buttons for creating user story
and topic is---https://redmine.ociotec.com/boards/11/topics/168
If you can do some effort to help with these issues, that will be great! Now the major issue we are facing is
- Burn down chart is not the actual chart we wanted
- Drag flow doesn't restricted by redmine default flow
RE: 【Need Help】Scrum 0.7.0 Usage Issue---Important FOR fixing(Redmine Calendar can not display) - Added by Stanislas Dourdin over 9 years ago
Regarding how noob I am in Ruby and in using Scrum, I am afraid I actually can't do anything for you.
I need to up competence in both domains but if I find something, I will tell you.
RE: 【Need Help】Scrum 0.7.0 Usage Issue---Important FOR fixing(Redmine Calendar can not display) - Added by Emilio González Montaña over 9 years ago
Solved in #847, it will be released on Scrum v0.9.1.