Private shortcut set is named using a composition with its owner user display name.
I found some situations where getting the user display name during the phase the shortcut is dinamically created may end in unexpected behavior, in particular, calling twice to field storage definition initialization.
In addition to that, there is no point of adding the user display name to the user's own private shortcut set.
The name for the own private shortcut set will be just "Private" and "User's private" when the current and owner user differs. Also by this way the system messages "Add to xxxx shortcuts" and "Remove from xxxx shortcuts" will be closer to natural language.
Remember that private shortcuts are never visible for any user rather than their owner, even those with administrative permissions cannot view or edit them.
Fixed
1.0
Code
Issue #3364945 by manuel.adan: Set private shortcut set name accordingly...
Automatically closed - issue fixed for 2 weeks with no activity.