Project

General

Profile

Defect #1373

Error when trying to add PBI or tasks into a sprint backlog

Added by Foucault Dupleix over 4 years ago. Updated over 4 years ago.

Status:
New
Priority:
High
Category:
Sprint board
Target version:
-
Source:
Customer
Detected on version:
Blocked:
No
Alone:
Milestones:
Sprint:

Description

Hello,

We configured Scrum plugin yesterday, and we have errors when trying to import massive old trackers.

Here is the situation :
  • On a new sprint, if we create new issues (no matter the tracker type), we don't have any problem.
  • If we massively transfer old issues (on different tracker types) into this sprint, for some of them, the process cannot be completed and a blank page with following error appears (InternalError.png)
  • From this moment, we are unable to add anything into the sprint, leading to the following blocking error (RedError.png)

We are pretty sure that some issues are blocking the sprint, because if we remove some of them, the sprint works properly again.

Are you aware of this problem? Do you have a workaround for it?


Files

InternalError.png (16 KB) InternalError.png Foucault Dupleix, 2017-05-11 10:08
RedError.png (44.5 KB) RedError.png Foucault Dupleix, 2017-05-11 10:12
#1

Updated by Foucault Dupleix over 4 years ago

Edit: I forgot to give you servers logs when trying to add a new issue to the sprint :

log/production.log

  Rendered plugins/redmine_agile/app/views/issues/_agile_data_fields.html.erb (0.5ms)
  Rendered plugins/redmine_checklists/app/views/issues/_checklist_fields.html.erb (0.9ms)
  Rendered plugins/redmine_checklists/app/views/issues/_checklist_fields.html.erb (0.8ms)
  Rendered plugins/redmine_checklists/app/views/issues/_checklist_form.html.erb (3.5ms)
  Rendered issues/_form.html.erb (42.6ms)
  Rendered attachments/_form.html.erb (2.0ms)
  Rendered issues/new.html.erb within layouts/base (49.2ms)
  Rendered plugins/scrum/app/views/scrum_hooks/_head.html.erb (0.2ms)
  Rendered plugins/scrum/app/views/scrum_hooks/_scrum_tips.html.erb (0.1ms)
Completed 200 OK in 183ms (Views: 71.6ms | ActiveRecord: 8.0ms)
Started POST "/scrum/9/create_pbi" for 192.***.*.** at 2017-05-11 09:59:45 +0200
Processing by ScrumController#create_pbi as JS
  Parameters: {"utf8"=>"✓", "back_url"=>"http://****/sprints/9", "issue"=>{"tracker_id"=>"19", "sprint_id"=>"9", "subject"=>"Test a supprimer", "status_id"=>"1", "priority_id"=>"4", "assigned_to_id"=>"", "due_date"=>"", "estimated_hours"=>"", "done_ratio"=>"0", "custom_field_values"=>{"27"=>"", "57"=>"", "62"=>"1"}, "description"=>""}, "create"=>"Créer", "sprint_id"=>"9"}
  Current user: ******* (id=102)
Exception: #<NoMethodError: undefined method `>' for nil:NilClass>
  Rendered plugins/scrum/app/views/scrum/create_pbi.js.erb (1.4ms)
Completed 200 OK in 43ms (Views: 3.2ms | ActiveRecord: 5.2ms)
#2

Updated by Emilio González Montaña over 4 years ago

Taking a look to your log file it seems the error is not in Scrum plugin, redmine_agile is the first line in the stack trace.

Anyway I need more details about how to reproduce, when you say transfer PBIs, you mean select issues of a project, edit massively and changing only Sprint field?

I fixed bug #1344, it could also fix your case, for latest version (not published yet). If you want early access to that fix via SVN repo please consider Patreon support :)

#3

Updated by Emilio González Montaña over 4 years ago

  • Description updated (diff)
#4

Updated by Foucault Dupleix over 4 years ago

Thanks a lot for your fast answer.

" Anyway I need more details about how to reproduce, when you say transfer PBIs, you mean select issues of a project, edit massively and changing only Sprint field "
=> Yes, it's exactly that. I select several issues in a project, then I right clic to massively change the sprint (and only the sprint). Some of them are correctly moved to the sprint, and when one of them encounters the error, remaining items are not moved to the sprint.
From this moment, the sprint is corrupted and we are not able to add issue on it.

The logs above are not directly linked to the massive move, but to the creation of a new PBI after the "corruption" of the sprint
You are right, it might be linked to be the Agile plugin. But the error seems to be raised in create_pbi function, which is hosted in Scrum directory, right? We compared the log stack of a correct PBI creation and a failed PBI creation, and the difference seems to be located in this function.

We will of course consider patreon support if we are sure that a new version will correct our problem :)

Also available in: Atom PDF