Project

General

Profile

Defect #1260

Automatic issue assignment outside of Scrum board?

Added by Lorem Ipsum almost 8 years ago. Updated almost 8 years ago.

Status:
Rejected
Priority:
Urgent
Category:
General
Target version:
-
Source:
Development
Detected on version:
Scrum v0.16.1
Blocked:
No
Alone:
Milestones:
Sprint:

Description

Since we updated the scrum plugin in our Redmine system we see that when we update an issue, the issue automatically gets assigned to the user that updated the issue instead of the user that is selected. Could this be due to a change in the Scrum plugin?

#1

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

  • Status changed from New to Rejected
  • Target version deleted (Scrum v0.16.2)
Plugin (since Scrum v0.15.0, #1173) auto assigns current user to the task when all of these conditions exists:
  1. Issue is a task.
  2. Scrum module is enabled.
  3. Task status changed.
  4. Assignee is empty (please take care issue is really assigned, maybe you have a task without assignee but it has effort from doers, so you still see the orange mini-post-its).
  5. Task new status is not New (the first one in plugin settings).
Plugin also auto clear assignee when all of these conditions exists:
  1. Issue is a task.
  2. Scrum module is enabled.
  3. Task status changed.
  4. Task new status is New (the first one in plugin settings).

Please check this, if you still thinks that you have a bug, please tell me.

Also available in: Atom PDF