Actions
Patch #6171
closedPersist 'locked' users across updates
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
Related issues
Actions