Project

General

Profile

Defect #1240

Task is assigned to none immediately after it's created

Added by Bartosz Firyn almost 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Category:
Issues list & form
Target version:
Source:
Development
Detected on version:
Blocked:
No
Alone:
Milestones:
Sprint:

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


Subtasks

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

Updated by Bartosz Firyn almost 5 years ago

I found that this specific functionality has been probably introduced by #1176. The ticket title is "Auto assign task when status is not new", but I think that current implementation is oversimplified. I think it should rather assume the following:

  • New task with new status should be auto assigned to creator if assignee is empty (noone),
  • New task with new status should be assigned to assignee when assignee has been selected upon creation.
#2

Updated by Bartosz Firyn almost 5 years ago

Please ignore my comment above. One more time. I think these should be the assumptions for auto assignment:

  • New task with not-new status should be assigned to creator if assignee is empty,
  • New task with not-new status should be assigned to assignee when assignee has been selected upon creation.
#3

Updated by Bartosz Firyn almost 5 years ago

Attached you can find a patchset for this change. It fixes this defect.

#5

Updated by Emilio González Montaña almost 5 years ago

  • Status changed from New to In progress
  • Target version set to Scrum v0.16.0
  • Sprint set to Sprint 31

This is not really a bug, it's an intentional feature, tasks in new status must not have assignee, this feature removes assignee for tasks when the status is new.

This behaviour is applied when the task is created, but also when a task in other status with assignee is moved to new status.

If you want to create tasks with assignee, best way it's to create "in progress" status (take care your workflow settings allows this).

Nevertheless, I will modify the plugin to check if Scrum module is enabled for the task project before patch issue behaviour...

#6

Updated by Emilio González Montaña almost 5 years ago

I've also added a new setting to the plugin called Clear assignee for tasks in new status, so if you want to disable this behaviour you can do it (is enabled by default).

#7

Updated by Emilio González Montaña almost 5 years ago

  • Status changed from In progress to Resolved
#8

Updated by Emilio González Montaña almost 5 years ago

  • Subject changed from Task is assigned to noone immediately after it's created to Task is assigned to none immediately after it's created

Also available in: Atom PDF