Project

General

Profile

Actions

Patch #6171

closed

Persist 'locked' users across updates

Added by ciaran jessup over 13 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Low
Assignee:
-
Category:
Issues
Target version:
-
Start date:
2010-08-18
Due date:
% Done:

0%

Estimated time:

Description

Currently when a user has been marked as 'locked' if an update occurs to an issue that is assigned to that user, that update will also remove the assigned (and locked) user. (You will see two journal entries informing you of this)

I think (personally) that it would be better if the assigned_to user was left un-touched when an unrelated change is made. (There is of course an argument around whether it is even valid for an issue to be assigned to a locked issue..but in my use case this is currently the case :( )

Please find attached a patch that does at least stop this behaviour (it does have the side-effect that the currently assigned user can appear twice in the list if that user isn't locked)


Files

display_locked_users_on_update.diff (922 Bytes) display_locked_users_on_update.diff ciaran jessup, 2010-08-18 16:41

Related issues

Is duplicate of Redmine - Defect #8884: Assignee is cleared when updating issue with locked assigneeClosed

Actions
Actions #1

Updated by Go MAEDA over 7 years ago

  • Is duplicate of Defect #8884: Assignee is cleared when updating issue with locked assignee added
Actions #2

Updated by Go MAEDA over 7 years ago

  • Status changed from New to Closed

Fixed by #8884 (Redmine 1.2.0).

Actions

Also available in: Atom PDF