Patch #6171

Persist 'locked' users across updates

Added by ciaran jessup over 7 years ago. Updated 12 months ago.

Status:ClosedStart date:2010-08-18
Priority:LowDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:-

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)

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


Related issues

Duplicates Redmine - Defect #8884: Assignee is cleared when updating issue with locked assignee Closed

History

#1 Updated by Go MAEDA 12 months ago

  • Duplicates Defect #8884: Assignee is cleared when updating issue with locked assignee added

#2 Updated by Go MAEDA 12 months ago

  • Status changed from New to Closed

Fixed by #8884 (Redmine 1.2.0).

Also available in: Atom PDF