Project

General

Profile

Defect #1240

Task is assigned to none immediately after it's created

Added by Bartosz Firyn about 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Normal
Category:
Issues list & form
Target version:
Scrum v0.16.0
Source:
Development
Detected on version:
Scrum v0.15.0
Blocked:
No
Alone:
Milestones:
Sprint:
Sprint 31

Description

Hi,

The problem lies in the fact that immediately after Task is created (from both issues list and sprint board) it's assigned no noone even if user selected assignee upon creation. This issue has been introduced in Scrum v0.15.0. Previously it was working well.

The problematic code is in lib/scrum/issue_patch.rb:

before_save :update_assigned_to, :if => lambda {|issue| issue.status_id_changed? and issue.is_task?}

After I commented it out, the task creation works well. What was the intention of :update_assigned_to when it was created? Because when I look at the code I see it changing assignee, but I do not understand why it should happen.

The w/a is to edit lib/scrum/issue_patch.rb and comment this line.

Moreover, such problem appears even when Scrum plugin is not enabled for a project...

Files

0001-Fix-auto-assign-task-when-status-is-not-new.patch (901 Bytes) 0001-Fix-auto-assign-task-when-status-is-not-new.patch Bartosz Firyn, 2016-11-10 17:48
0001-Auto-assign-non-new-ticket-only-if-assignee-is-not-s.patch (885 Bytes) 0001-Auto-assign-non-new-ticket-only-if-assignee-is-not-s.patch Bartosz Firyn, 2016-11-10 18:04

Subtasks

To do #1243: Add setting to disable assignee reset & check Scrum module is enabledResolvedEmilio González MontañaActions

Also available in: Atom PDF