My issue is similar to: https://answers.atlassian.com/questions/250787/after-renaming-usernames-in-jira-6-1-4-worklogs-do-not-expand-author-correctly-in-rest-api
Basically, I renamed a user and it works most places - but not everywhere. Specifically, I have a few plugins (like Watchers plugin and JJUPIN) that seem to be using the user_key instead of lower_user_name. Is there a better solution to doing a complete rename other than the laborious SQL queries mentioned in the linked article?
As mentioned by @Luther, there is not a pretty solution to this. There will be ugly SQL queries, chewed finger nails, sweat, and possibly tears when you have to rename your user's login inside JIRA.
Thanks for providing confirmation of the issue. My solution was to contact the plugin vendors and let them know of the issue caused by Atlassian's design of user names. Apparently no one at Atlassian ever gets married ;) Otherwise this issue would be much more obvious!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If there is, I haven't found one. Until JIRA modifies how it stores usernames in SQL, it is going to be difficult. They use pointers currently to handle name changes, instead of updating the user_key (which shouldn't be a 'key' in the first place).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.