Alfa Product Team added a comment - 10/Mar/2022 2:33 PM - edited CONFSERVER-34386 said If you'd like to describe more how this would help in your own use of Confluence, we may be able to provide better guidance. I've got some context from a real world example. Pre-requisites user ids are in some sense or other derived from names (yes, with hindsight we'd set up our user accounts with an id that is independent from user name, but we're not that unusual in taking a "you're not a number" approach to users) user changes their name - doesn't matter why, could be switching to/from married name, could be any other reason, legally they can do this We have nice LDAP integration, and Confluence recognises that it's the same user account, just with an updated user id. Hurray... no need to go SQLing the database to maintain that linkage. What's the problem? Now when people are sharing links from my colleague's personal space, there it is in the URL, their old user id - because that was carved in stone into the space key when they set up their personal space. And that might not seem a big deal, it's just some characters in a URL, but changing your name is something which may really matter to an individual. As system administrators we very much respect our colleague's decision to change their identity, but this reminder from the past keeps coming up, and as things stand there's nothing we can do to move forwards. It would be great to have an option in the software to migrate the personal space key to match the user's current userid. But if there was a manual process (exporting content and reimporting, or moving things around spaces temporarily) that doesn't involve downtime and SQLing the db, that would get us to a better place than we are right now.

Guilherme V. (Inactive) added a comment - 16/Apr/2020 7:45 PM Internal Notes I have raised this new ticket because the old one did not have any UIS since that time it wasn't implemented. This one we can keep track of recent cases and increase the UIS.