Nitish, thanks, I was able to use that statement in a function which uses usermigration to update them all automatically, as the other statements do. I have added those statements to my comment above.

Hi erin,
Adding the below script could further enhance it

Update searchrequest Set REQCONTENT = Replace (REQCONTENT, 'OLDVAL' , 'NEWVAL');

because sometimes there are filters stored in such a fashion as
project=JRA and assignee= OLDVAL

Regards,
Nitish

Here is the PostGreSQL script for JIRA 4:

update changegroup set AUTHOR=newusername from usermigration where AUTHOR=oldusername;
update changeitem set OLDVALUE=newusername from usermigration where OLDVALUE=oldusername;
update changeitem set NEWVALUE=newusername from usermigration where NEWVALUE=oldusername;
update columnlayout set username=newusername from usermigration where username=oldusername;
update component set LEAD=newusername from usermigration where LEAD=oldusername;
update external_entities set NAME=newusername from usermigration where NAME=oldusername;
update favouriteassociations set USERNAME=newusername from usermigration where USERNAME=oldusername;
update fileattachment set author=newusername from usermigration where author=oldusername;
update filtersubscription set username=newusername from usermigration where username=oldusername;
update jiraaction set AUTHOR=newusername from usermigration where AUTHOR=oldusername;
update jiraaction set UPDATEAUTHOR=newusername from usermigration where UPDATEAUTHOR=oldusername;
update jiraissue set reporter=newusername from usermigration where reporter=oldusername;
update jiraissue set assignee=newusername from usermigration where assignee=oldusername;
update jiraworkflows set creatorname=newusername from usermigration where creatorname=oldusername;
update membershipbase set USER_NAME=newusername from usermigration where USER_NAME=oldusername;
update OS_CURRENTSTEP set owner=newusername from usermigration where owner=oldusername;
update OS_CURRENTSTEP set caller=newusername from usermigration where caller=oldusername;
update OS_HISTORYSTEP set owner=newusername from usermigration where owner=oldusername;
update OS_HISTORYSTEP set caller=newusername from usermigration where caller=oldusername;
update portalpage set  username=newusername from usermigration where username=oldusername;
update project set lead=newusername from usermigration where lead=oldusername;
update projectroleactor set roletypeparameter=newusername from usermigration where roletypeparameter=oldusername and roletype='atlassian-user-role-actor';
update schemepermissions set perm_parameter=newusername from usermigration where perm_parameter=oldusername and perm_type='user';
update searchrequest set authorname=newusername from usermigration where authorname=oldusername;
update searchrequest set username=newusername from usermigration where username=oldusername;
update trustedapp set CREATED_BY=newusername from usermigration where CREATED_BY=oldusername;
update trustedapp set UPDATED_BY=newusername from usermigration where UPDATED_BY=oldusername;
update userassociation set SOURCE_NAME=newusername from usermigration where SOURCE_NAME=oldusername;
update userbase set username=newusername from usermigration where username=oldusername;
update worklog set author=newusername from usermigration where author=oldusername;
update worklog set updateauthor=newusername from usermigration where updateauthor=oldusername;
update customfieldvalue set stringvalue=newusername from usermigration where stringvalue=oldusername;
update userhistoryitem set username=newusername from usermigration where username=oldusername;
-- The following function employs string replacement to update filters and may be damaging if any of the old usernames are also words that exist in the filter definition as a non-username string. Uncomment to use this at your own risk.
-- create language plpgsql;
-- create or replace function updatejirafilters() returns char as $$
-- declare
-- line record;
-- begin
-- for line in select * from usermigration loop
-- update searchrequest set REQCONTENT=replace(REQCONTENT, line.oldusername , line.newusername);
-- end loop;
-- return 'done';
-- end;
-- $$ language plpgsql;
-- select updatejirafilters();

username in LDAP is changeable, usually thats the uid. The username is in many companies connected to the name of a user (like mail-address or abbreviations of a users fullname). If that user's name is changed usually the uid will be changed accordingly (at least in our company thats done like that).
You can ship around that obstacle by using a unique identifier which consists of unconnected elements (like a random number/character combination). But its not readable anymore (because l75gd is much less understandable as fst (e.g. in my case)).

The Design Flaw is that you cant change the username while the system is running and/or without having a automated possibility for it (like a trigger in the AD/LDAP which syncs the JIRA instance). I guess if the API would have a ChangeUserName method i wouldnt care if there is that kind of design flaw (of course there must not be a downtime for reindexing, in our jira that would be around 30 to 45min.)

I dont say confluence doesnt have sideeffects on renaming without reindexing, but at least it can still operate

p.s. i have seen usernames which say old account/dont use me i guess thats the thing that wants to be avoided

Hello Tom,

you got it.
That is the whole point of this issue, which is open since such long time.

Atlassian uses as userid the same username which is input by the users at login and needed to do user authentication over LDAP.
Instead, they should use a hidden number / id, as it is in every good database design.
But they don't want to and prefer to stick year after year to their original mistake!

Bettina

Bettina,

Is in LDAP the username changeable ?
In that case there must be an underlying identifier that remains the same.

Hello Tom,

the problem is that in case of external user management - a widely used Jira feature - the username MUST be identical with the username that comes over LDAP.
In my example, I have to keep the Jira username up-to-date with our Active Directory.
Every time a user is renamed in the Active Directory, I also have to change the username in Jira.
You can replace "username" with "userid", the problem stays the same, even if nobody else than me (as Jira Admin) were able to see the username / userid.

So the username / userid is NOT meaningless, since it is exchanged with other systems!

Cheers
Bettina

I don't see why this is such a problem for Atlassian to follow up on.
Basic rule is simple.
Id's should never be visible to users, and be meaningless.
The username becomes userid, and the full name belonging to that user-id gets shown everywhere.
This way the user-id never needs to be changed, only 1 change is needed when the release with this change is done.

I'm afraid that this improvement will never be implemented, but nevertheless I vote for it since it's a MUST HAVE in my opinion.

As a new JIRA customer, I must say... This is an epic/ridiculous fail for Atlassian.

We are in the same situation, we need to merge two JIRA instances where there are cases of a single user having two different userids on those instances. So we need to rename those users on one of the instances, but we can't.

And this is flying around, opened and voted for, since 2003. LOL.

1. A solution that depends on a production restart and reindex is not a practical solution to this problem
2. The fact that my username seems to be the primary key, littered about throughout the database as the foreign key on however many tables, seems like really smelly development to me.

I used a simpler form

Update searchrequest Set REQCONTENT = Replace (REQCONTENT, 'OLDVAL' , 'NEWVAL');

It worked well!

I'm not going to pretend to be skilled at SQL scripts, but the following seems to work for replacing values in the reqcontent column:

update JIRASchema.searchrequest set reqcontent=replace(Cast(reqcontent AS NVARCHAR(Max)),'oldvalue','newvalue');

I got the idea from here - http://stevenharman.net/blog/archive/2007/12/30/a-better-search-and-replace-for-your-database.aspx

Hi
The script

update xxxx set xxx=yyyy where xxx=zzz

it is working fine.
Just that 1 point is missing.

The search request column has a table "request".
It has filtered stored in the form of SQL search.
eg:

SearchRequest id="10223" name="All Cranial" author="prossj" user="prossj" project="10011" request="reporter = alexp ORDER BY key DESC" favCount="1"/>

I find that the scripts will not correct that "alexp".
Please look into it!

The last mentioned db schema changes have been in 4.0 and 3.12. As 4.0 were merely db type migrations to larger data types i guess you should be save with the 3.13 scripts mentioned here.

Has anyone tried this on 4.2.0 (or, I guess, 4.2.1) yet? Particularly with MySQL? We have some users to rename.

Rain, i guess Srinis Oracle Script is the latest posted here. OracleDB-UserNameUpdate-SQL-Jira3.13.4-Enterprise.txt. From 3.13 to 4.1 there werent any username relevant tablechanges as far as i know. Whoever uses the latest version is welcome to be the pioneer to try it

Our LDAP directory has capital letters in the username (eg. AustinS). If i create similar users in JIRA in lowercase (austins)(JIRA doesnt support uppercase), will the LDAP integration be possible directly.(USING THE DATABSE EDITING WORKAROUND)

Anyone know if Peter's script works with 4.2?

Please add this. Our IT person just asked me for help with the typical case (user gets married). She created a new JIRA user with the same groups and was going to just try to reassign and change reporter on all the tickets the old username had (700+). Of course, due to restrictions on editing closed issues, plus various permission schemes we've set up, even I am not able to bulk change the issues. I now have to start combing through our various permissions and project setups just so that I can get bulk change working. I'm sure I'll get it going eventually but it's a hokey workaround.

Thanks,

We are running JIRA for our company using LDAP as well, and every few months it seems we have a request to change user names due to marital status. This feature is very much needed and would save us from so many headaches and hours of explanation to users.

I have successfully (I hope!) renamed a user using Frank Stiller's SQL scripts. Thank you, Frank! I added one table to the script: userhistoryitem, discovered when I grepped the .xml backup for the oldusername after running Frank's script.

update userhistoryitem x inner join usermigration u on x.username = u.oldusername set x.username = u.newusername;

Atlassian, you should officially sanction and support Frank's script at the very least.

Please hurry!

Nancy, I am delighted you are able to keep your sense of humor. :-S

Well, we have been live with Jira for one month and have received our first user rename request. I approach this with serious trepidation and much frustration. This user cannot log in at all now because our IT department has already renamed her username. Atlassian, you have really dropped the ball on this one. I am really embarrassed to explain this to my user community! Please hurry!

I think the best approach to solving this is a plugin that does what all the different versions of the scripts out there do.

1. It can also check the version of the database schema to know what to change
2. It can handle the more complex cases where the username is embedded in a parameter to a scheme, e.g. notification scheme with a Custom User Field parameter
3. It can handle renaming a user and also merging two userids into one.
4. It can check for existing users with the same name

Testing it is likely to be the hardest thing. How do I set up a JIRA instance with a particular userid embedded everywhere it can be?

~Matt

p.s. If I had a DolLorean DMC-12 and the rest, I've got a few other things to fix first before JRA-1549.

I will stress my previous comment once again...

I could care less how this information is stored in the database. All I want is a way to rename a user. It doesn't happen every day, so some supported function in the administration section where I can enter/pick a user and enter their new name which does whatever it needs to do in order to make everything work (update all the username fields like the scripts attached to this post do) would be a perfectly acceptable answer in my opinion. Even just a supported script to download and run that I don't have to dig through an issue to find would be fine. Much better than the string replacement in XML which could replace much more than you really want it to.

Great work Matt Doar,

Now we only need get the hold of George McFly, Dr. Emmett "Doc" Brown, a slightly modified DeLorean DMC-12 and some plutonium to feed the flux capacitor and this thing will be sorted in no time..

Regards

Jonas

I found this on a Confluence documentation page, and it goes some way to explaining the historical decision not to use the userbase id field in JIRA.

"Since it is not guaranteed that users will be stored in the confluence database (eg. using external user management), the username instead of an id is used as the foreign key."

Vlastimil,

I've pondered doing this as a plugin too. Let us know how you get on.

~Matt

Now that you've mentioned you are building a plugin, Atlassian is going to stop working on any supported solution - it has happend before with cluster support. However if you can make it work in less than 7 years you'll be ahead of the curve and will make at least 443 people very happy. Thanks for stepping up to the plate.

P.S. As frustrating as some of these road blocks are I still love what Jira can do.

Hi all,

I'm just working on plugin which allows user rename and user merge in jira 4.1.2 directly from admin console. Work is very promising for now.

I've only just read the August update which states that we're going to be waiting another 6 months in all likelihood. Is there any way of codifying the recommended workarounds so that Jira would apply the database changes itself? I really think that, after 7+ years, we could do with a tactical solution rather than waiting for the mythical Crowd integration to happen. What do you reckon Atlassian? Cheers, Mike

good news for me, personally, is that my senior managers haven't complained when I suggested we could save money by not renewing our jira, confluence and greenhopper licences for a while, which expired yesterday, either until there's a compelling new feature we can't live without which includes the authentication model i.e. the ability to rename users.

We would love to have a supported solution for this use case at least for mass mutations such as renaming n user accounts when we link them to LDAP servers. Our current solution which we applied once when migrating our own user database to LDAP authentication and which we will apply again migrating one of our customer which we cater ActiveDirectory services to is dumping to XML JIRA, transforming and reloading. This takes days of quality assurance until we are 100% sure that the result is fully consistent again.

I didn't want to create any different tables, so I just changed them all to a format like

UPDATE [table] SET [column] = [newvalue] WHERE [column] = [oldvalue];

I didn't get any MySQL errors. The only error I did get was an application error when trying to look at the user details page. Since my user had already been in the application using their new username, the external_entities table already had an entry with that new username so when I updated the old one it made a duplicate entry which the application apparently doesn't like, so I had to remove that. So if your user has already been using the application with their new username, I wouldn't bother with the external_entities update, it hasn't seemed to cause any issues for me having both the old and new.

When you say basically, what modifications did you make?

Also, were any MySQL errors observed or Tomcat application errors?

I basically ended up using the one from http://jira.atlassian.com/browse/JRA-1549?focusedCommentId=170640&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-170640

Which one?

I just used one of the sql scripts and that got the job done for me. Atlassian, please listen to your users here. Our problem is WE NEED TO RENAME USERS, but usually not that often. In my opinion, a supported script is a perfectly acceptable solution.

We urgently need this too. Am not allowed to use the scripts unless they are officially supported by Atlassian. Please deliver officially supported scripts or implement it in JIRA.

7 years...really? Very disappointing Atlassian. I'm sure this would have been a much easier change 7 years ago when there was 7 years less new code depending on the user name as the id field. WAY past time to pay down some technical debt.

Several times I have been tempted to use the scripts fix several of our users, but I always stopped because I don't know if any of the extensions we are using store the information. This is the classic example of not using data that could be changed as a key.

Is this safe to use with the extensions? Is there a good way to tell?

The latest 3.13 scripts should be sufficient as there are no db changes for 4 as i wrote 3 comments ago. What is more relevant is what db engine your are targeting? Thats the best confirmation you get so far. And reindexing is required, restarting maybe recommended.

Thanks, will ensure to restart Jira after the renames. Can someone post the latest version of the script that has been confirmed to work with version 4?

Keep in mind that even updating the database isn't going to be enough. JIRA caches a lot of information that is only read during application start-up, as I learned the hard way, so updating the database will only work for you if you intend to restart JIRA afterwards. (Some changes take effect immediately, but other fields are cached indefinitely.)

brutal.... all we need is a supported SQL script. c'mon atlassian...

same problem here, need a script to run, but there are so many update statements on here I don't know which one is valid for Jira 4 ...

The base thing is. The Scripts mentioned here are running for a specified Database-Engine and a specific JIRA Version. So in your case i guess its: JIRA 4.1.2 and Oracle. So i would try Srini's attached Oracle-Script. In the table usermigration you write oldusername: jdoe newusername janedoe and then you synchronize jdoe.

I guess that should do it, except you need a sql-server script also, but you are not running two different databases, are you?

Here's the jira version upgrade details:

Mixed user mode means is that, we are using the same JIRA in company and other persons who are not company employees. We want company employees login with active directory authentication and others login with jira userbase authentication.

Let me try to explain our problem step by step.

• Jane Doe started working in our company. Jira user and active directory "jdoe" is defined for her.
• Jane Doe quited from our company. jdoe deleted from active directory but jira user only disabled.
• John Doe started working in our company. Active directory user "jdoe" is defined but jira user "jdoe" couldn't be defined because "jdoe" was already defined.
• Now we want to change Jane Doe's user "janedoe" and use "jdoe" for John Doe.

Which script/s can we use for this change?

Thanks.

I am still missing which database engine you are running, like MySQL, Oracle or such. And i am interested what you mean by mixed user mode? You mean users which are not in den AD are authenticated locally? I can maybe test the latest JIRA Release for MySQL, but i cant promise you that will be soon, depends what database changes have been done since 3.13, doesnt seems much, so probably the 3.13 scripts can be used on 4.1 also, only found this: 4.0 db changes.

We upgraded JIRA version to 4.1.2 and trying to use jira mixed user mode (Active directory + Jira user management). Some users are different from active directory user and we want to migrate jira username to ldap username. Can you tell us which script is compatible with jira 4.1.2 ?

Thanks.

If we use "find and replace from xml" method for renaming jira users, there will be wrong updates because of some usernames enlisted in jira issue comment and description fields. How can we solve this problem. We don't want to change issue contents.

we just had an email from atlassian to renew our maintenance contract - US$4000. Guess what, I'm going to rush to pay this just as fast as Atlassian have been rushing to fix this issue!

— here's what I emailed them —
Dear Atlassian,
we feel no need to renew our maintenance contract with any degree of
urgency, just as Atlassian have felt no need to fix some significant
outstanding issues namely

JRA-1391 Renaming groups after creation (7 years old)
JRA-1549 Ability to rename a user (6.5 years old)

Let us know when you fix these and we'll consider spending more money.

— here's the reply (email munged deliberately)---
From: Jason Caragan <salesXX@XXatlassian.com>

Hi Paul,

Thanks for your feedback and sorry to hear you won't be renewing. I'll
be sure to forward your concerns to our Products team and hope to see
them addressed with a future release.

Cheers,
Jason
Jason Caragan

One vote from us also. Over here, some people DO get married and change names...

Come on, guys, this is basic stuff here. Export all your data, do a find/replace, then re-import all your data is a really crappy solution no matter what the problem is.

Also keep in mind that for every user who makes a login and posts and/or votes, there's likely a couple dozen out there that just shake their heads and start looking for alternatives.

Atlassian sales team was kind enough to send us an informational quote to renew our Jira licence.

We were kind enough to reply:

Thank you for your informational quote. We will gladly renew the licence after bugs affecting us have been resolved, namely:

• JRA-2364 Hide Time Tracking estimates from certain users (e.g. customers)
• JRA-1391 Renaming groups after creation.
• JRA-1549 Ability to rename a user

All of these bugs have been open for seven years now!

Atlassian, treating your customers this way is not a way to do business. If everybody stops paying for Jira, maybe then they'll reconsider. I urge you to do the same.

7 years and it's now the number 5 on the most popular issues, and no assignee? Com'on!

Hi Frank, I have checked the search storedproc again. The tables listing the username are listed in the attached .csv file. I will be searching through our production db soon and will be able to add additional tablenames. I will list these once retrieved.(This is only a test jira install)

Hy Earl,
by a quick lookthrough the it looks good. But it seems very generic. The seasoned scripts mentioned here are only looking in columns identified to be username-relevant. With your storedprocedure you are replacing every column in the database, do you? I guess that can be problematic. Like a group support and a user support (just a simple one i hope).
cheers Frank

I am new to the Jira environment. One of our staff have gotten married. I did some research and figured that its data and as such can be manipulated by sql if you're using sql. I have tested this on a test system but would welcome any comments from the more seasoned Jira Admins.
The search script does just that - searching for occurences of a particular data string. The find and replace does the very same thing except it replaces the 'string' found with any other data. Pls review and advise.
The Jira service needs to be shutdown when performing the change.

Funny part is Atlassian is not even providing any kind of updates here. As I mentioned below, if there is no intention now to fix this problem then just close this issue by saying WON'T FIX!

That way everyone gets a clear picture on what they should be doing rather than keep waiting without any ETA from Atlassian.

Thanks,
Amar

Completely agree with Jonas. I think the age of this issue and the number of votes clearly shows that just voting for the issue is NOT enough. I have stated a number of times on several issues that every major software company end of lifes their products. Forget backward compatibility, I have a number of scripts and other customizations I would gladly rewrite to gain many new features and fixes that Atlassian has used 'backward compatability' as an excuse for not adding or fixing.

Instead of complaining about users that verbaly show that this is a feature we should have had 5 years ago, maybe Atlassian could just fix the bug and close the issue? Further more i think this lack of feature is simpler to conduct if the database scheme is completely restructured, meaning that sure the database will not be backwards compatible, but who would try to upgrade and then downgrade without restoring the last dump?

Ubisoft, I have removed you from watching this issue as per my email to you about your autoresponder.

La requête #466814 - [JIRA] Commented: (JRA-1549) Ability to rename a user a été crée.

Pour effectuer un suivi, et/ou ajouter un commentaire, veuilliez répondre à ce courriel.
Cette requête sera traitée dès que possible.

Merci de votre collaboration, Your request 466814 - [JIRA] Commented: (JRA-1549) Ability to rename a user has been created.

For a follow-up, and/or add comments, please reply to this e-mail.
This request will be treated as soon as possible.

Thank you for your cooperation,

Votre requête / Your request
Issue (View Online/jira.atlassian.com/browse/JRA-1549>)

Key: JRA-1549/jira.atlassian.com/browse/JRA-1549>
Issue Type: http://jira.atlassian.com/images/icons/improvement.gif /jira.atlassian.com/browse/JRA-1549> Improvement
Status: http://jira.atlassian.com/images/icons/status_open.gif Open
Priority: http://jira.atlassian.com/images/icons/priority_major.gif Major
Assignee: Unassigned
Reporter: Michael Phillimore-Brown/jira.atlassian.com/secure/ViewProfile.jspa?name=firewater>
Votes: 384

Operations
http://jira.atlassian.com/images/icons/bullet_creme.gif View all/jira.atlassian.com/browse/JRA-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel>
http://jira.atlassian.com/images/icons/bullet_creme.gif View comments/jira.atlassian.com/browse/JRA-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel>
http://jira.atlassian.com/images/icons/bullet_creme.gif View history/jira.atlassian.com/browse/JRA-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:changehistory-tabpanel>

Ability to rename a user/jira.atlassian.com/browse/JRA-1549>
Updated: 30/Apr/10 11:42 AM Created: 08/Apr/03 7:57 AM

The following comment has been added to this issue: [ Permalink/jira.atlassian.com/browse/JRA-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193131#action_193131> ]
Author: Gili/jira.atlassian.com/secure/ViewProfile.jspa?name=cowwoc>
Date: 30/Apr/10 11:42 AM
Comment:

Guys, this is getting spammy. Please stop posting "me too" comments and just vote for the issue. Votes are enough.

Also, can someone please unsubscribe ubisoft from this issue? Their auto-responder only makes things worse.

Project: JIRA/jira.atlassian.com/browse/JRA>
Components: Administration
Affects Versions: 2.0.2
Attachments: D3904554-8F1C-8F48-9B44-FF092AD4E845, D3904554-8F1C-8F48-9B44-FF092AD4E845, D3904554-8F1C-8F48-9B44-FF092AD4E845, D3904554-8F1C-8F48-9B44-FF092AD4E845, jira_renameuser_all.sql, OracleDB-UserNameUpdate-SQL-Jira3.13.4-Enterprise.txt, renameuser.sql

Description

As Jira starts to take off, invariably people play around with the system and begin to use it in anger gradually. During this time they sometimes find that the original username they created is not really the best they could have chosen. However, at the moment they cannot change this.

Would it be possible to change your login id as part of your profile? I know this is often a tough thing to do, but many of our users would find it useful.

Cheers!

This message was automatically generated by Atlassian JIRA/www.atlassian.com/c/JIRA/10140> Enterprise Edition, Version: 4.1.1-522 - Bug/feature request/jira.atlassian.com/default.jsp?clicked=footer>.
If you think it was sent incorrectly, contact one of this server's administrators/jira.atlassian.com/secure/Administrators.jspa>.

Guys, this is getting spammy. Please stop posting "me too" comments and just vote for the issue. Votes are enough.

Also, can someone please unsubscribe ubisoft from this issue? Their auto-responder only makes things worse.

La requête #466807 - [JIRA] Commented: (JRA-1549) Ability to rename a user a été crée.

Pour effectuer un suivi, et/ou ajouter un commentaire, veuilliez répondre à ce courriel.
Cette requête sera traitée dès que possible.

Merci de votre collaboration, Your request 466807 - [JIRA] Commented: (JRA-1549) Ability to rename a user has been created.

For a follow-up, and/or add comments, please reply to this e-mail.
This request will be treated as soon as possible.

Thank you for your cooperation,

Votre requête / Your request
Issue (View Online/jira.atlassian.com/browse/JRA-1549>)

Key: JRA-1549/jira.atlassian.com/browse/JRA-1549>
Issue Type: http://jira.atlassian.com/images/icons/improvement.gif /jira.atlassian.com/browse/JRA-1549> Improvement
Status: http://jira.atlassian.com/images/icons/status_open.gif Open
Priority: http://jira.atlassian.com/images/icons/priority_major.gif Major
Assignee: Unassigned
Reporter: Michael Phillimore-Brown/jira.atlassian.com/secure/ViewProfile.jspa?name=firewater>
Votes: 384

Operations
http://jira.atlassian.com/images/icons/bullet_creme.gif View all/jira.atlassian.com/browse/JRA-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel>
http://jira.atlassian.com/images/icons/bullet_creme.gif View comments/jira.atlassian.com/browse/JRA-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel>
http://jira.atlassian.com/images/icons/bullet_creme.gif View history/jira.atlassian.com/browse/JRA-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:changehistory-tabpanel>

Ability to rename a user/jira.atlassian.com/browse/JRA-1549>
Updated: 30/Apr/10 11:12 AM Created: 08/Apr/03 7:57 AM

The following comment has been added to this issue: [ Permalink/jira.atlassian.com/browse/JRA-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193128#action_193128> ]
Author: amar goradia/jira.atlassian.com/secure/ViewProfile.jspa?name=amargoradia>
Date: 30/Apr/10 11:12 AM
Comment:

I echo Michelle. Please help and give us an update ASAP...

On Apr 29, 2010, at 8:23 AM, "Michelle Wetherill (JIRA)"

Project: JIRA/jira.atlassian.com/browse/JRA>
Components: Administration
Affects Versions: 2.0.2
Attachments: D3904554-8F1C-8F48-9B44-FF092AD4E845, D3904554-8F1C-8F48-9B44-FF092AD4E845, D3904554-8F1C-8F48-9B44-FF092AD4E845, jira_renameuser_all.sql, OracleDB-UserNameUpdate-SQL-Jira3.13.4-Enterprise.txt, renameuser.sql

Description

As Jira starts to take off, invariably people play around with the system and begin to use it in anger gradually. During this time they sometimes find that the original username they created is not really the best they could have chosen. However, at the moment they cannot change this.

Would it be possible to change your login id as part of your profile? I know this is often a tough thing to do, but many of our users would find it useful.

Cheers!

This message was automatically generated by Atlassian JIRA/www.atlassian.com/c/JIRA/10140> Enterprise Edition, Version: 4.1.1-522 - Bug/feature request/jira.atlassian.com/default.jsp?clicked=footer>.
If you think it was sent incorrectly, contact one of this server's administrators/jira.atlassian.com/secure/Administrators.jspa>.

I echo Michelle. Please help and give us an update ASAP...

On Apr 29, 2010, at 8:23 AM, "Michelle Wetherill (JIRA)" <jira@atlassian.com

La requête #466364 - [JIRA] Commented: (JRA-1549) Ability to rename a user a été crée.

Pour effectuer un suivi, et/ou ajouter un commentaire, veuilliez répondre à ce courriel.
Cette requête sera traitée dès que possible.

Merci de votre collaboration, Your request 466364 - [JIRA] Commented: (JRA-1549) Ability to rename a user has been created.

For a follow-up, and/or add comments, please reply to this e-mail.
This request will be treated as soon as possible.

Thank you for your cooperation,

Votre requête / Your request
Issue (View Online/jira.atlassian.com/browse/JRA-1549>)

Key: JRA-1549/jira.atlassian.com/browse/JRA-1549>
Issue Type: http://jira.atlassian.com/images/icons/improvement.gif /jira.atlassian.com/browse/JRA-1549> Improvement
Status: http://jira.atlassian.com/images/icons/status_open.gif Open
Priority: http://jira.atlassian.com/images/icons/priority_major.gif Major
Assignee: Unassigned
Reporter: Michael Phillimore-Brown/jira.atlassian.com/secure/ViewProfile.jspa?name=firewater>
Votes: 383

Operations
http://jira.atlassian.com/images/icons/bullet_creme.gif View all/jira.atlassian.com/browse/JRA-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel>
http://jira.atlassian.com/images/icons/bullet_creme.gif View comments/jira.atlassian.com/browse/JRA-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel>
http://jira.atlassian.com/images/icons/bullet_creme.gif View history/jira.atlassian.com/browse/JRA-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:changehistory-tabpanel>

Ability to rename a user/jira.atlassian.com/browse/JRA-1549>
Updated: 29/Apr/10 10:23 AM Created: 08/Apr/03 7:57 AM

The following comment has been added to this issue: [ Permalink/jira.atlassian.com/browse/JRA-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193006#action_193006> ]
Author: Michelle Wetherill/jira.atlassian.com/secure/ViewProfile.jspa?name=mwetherill>
Date: 29/Apr/10 10:23 AM
Comment:

Atlassian, please help! We need this fixed! We are trying to integrate with LDAP but the user names in JIRA (and Confluence) do not match up. We need a way to correct all of the user names. What is the recommended approach? Is it still to try and do a find/replace in the XML export? Has someone from Atlassian reviewed the scripts posted on this issue and "approved" them?

Project: JIRA/jira.atlassian.com/browse/JRA>
Components: Administration
Affects Versions: 2.0.2
Attachments: D3904554-8F1C-8F48-9B44-FF092AD4E845, D3904554-8F1C-8F48-9B44-FF092AD4E845, jira_renameuser_all.sql, OracleDB-UserNameUpdate-SQL-Jira3.13.4-Enterprise.txt, renameuser.sql

Description

As Jira starts to take off, invariably people play around with the system and begin to use it in anger gradually. During this time they sometimes find that the original username they created is not really the best they could have chosen. However, at the moment they cannot change this.

Would it be possible to change your login id as part of your profile? I know this is often a tough thing to do, but many of our users would find it useful.

Cheers!

This message was automatically generated by Atlassian JIRA/www.atlassian.com/c/JIRA/10140> Enterprise Edition, Version: 4.1.1-522 - Bug/feature request/jira.atlassian.com/default.jsp?clicked=footer>.
If you think it was sent incorrectly, contact one of this server's administrators/jira.atlassian.com/secure/Administrators.jspa>.

Atlassian, please help! We need this fixed! We are trying to integrate with LDAP but the user names in JIRA (and Confluence) do not match up. We need a way to correct all of the user names. What is the recommended approach? Is it still to try and do a find/replace in the XML export? Has someone from Atlassian reviewed the scripts posted on this issue and "approved" them?

La requête #466181 - [JIRA] Commented: (JRA-1549) Ability to rename a user a été crée.

Pour effectuer un suivi, et/ou ajouter un commentaire, veuilliez répondre à ce courriel.
Cette requête sera traitée dès que possible.

Merci de votre collaboration, Your request 466181 - [JIRA] Commented: (JRA-1549) Ability to rename a user has been created.

For a follow-up, and/or add comments, please reply to this e-mail.
This request will be treated as soon as possible.

Thank you for your cooperation,

Votre requête / Your request
Issue (View Online/jira.atlassian.com/browse/JRA-1549>)

Key: JRA-1549/jira.atlassian.com/browse/JRA-1549>
Issue Type: http://jira.atlassian.com/images/icons/improvement.gif /jira.atlassian.com/browse/JRA-1549> Improvement
Status: http://jira.atlassian.com/images/icons/status_open.gif Open
Priority: http://jira.atlassian.com/images/icons/priority_major.gif Major
Assignee: Unassigned
Reporter: Michael Phillimore-Brown/jira.atlassian.com/secure/ViewProfile.jspa?name=firewater>
Votes: 381

Operations
http://jira.atlassian.com/images/icons/bullet_creme.gif View all/jira.atlassian.com/browse/JRA-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel>
http://jira.atlassian.com/images/icons/bullet_creme.gif View comments/jira.atlassian.com/browse/JRA-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel>
http://jira.atlassian.com/images/icons/bullet_creme.gif View history/jira.atlassian.com/browse/JRA-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:changehistory-tabpanel>

Ability to rename a user/jira.atlassian.com/browse/JRA-1549>
Updated: 29/Apr/10 4:03 AM Created: 08/Apr/03 7:57 AM

The following comment has been added to this issue: [ Permalink/jira.atlassian.com/browse/JRA-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=192984#action_192984> ]
Author: Martin Lopušek [CFH]/jira.atlassian.com/secure/ViewProfile.jspa?name=foster>
Date: 29/Apr/10 4:03 AM
Comment:

It shoud be good if any plugin would be created to rename user. Because this status is absolutely untenable. This is not about: JIRA - because you'got issue, but We've got issue, because we have jira.

Project: JIRA/jira.atlassian.com/browse/JRA>
Components: Administration
Affects Versions: 2.0.2
Attachments: D3904554-8F1C-8F48-9B44-FF092AD4E845, jira_renameuser_all.sql, OracleDB-UserNameUpdate-SQL-Jira3.13.4-Enterprise.txt, renameuser.sql

Description

As Jira starts to take off, invariably people play around with the system and begin to use it in anger gradually. During this time they sometimes find that the original username they created is not really the best they could have chosen. However, at the moment they cannot change this.

Would it be possible to change your login id as part of your profile? I know this is often a tough thing to do, but many of our users would find it useful.

Cheers!

This message was automatically generated by Atlassian JIRA/www.atlassian.com/c/JIRA/10140> Enterprise Edition, Version: 4.1.1-522 - Bug/feature request/jira.atlassian.com/default.jsp?clicked=footer>.
If you think it was sent incorrectly, contact one of this server's administrators/jira.atlassian.com/secure/Administrators.jspa>.

It shoud be good if any plugin would be created to rename user. Because this status is absolutely untenable. This is not about: JIRA - because you'got issue, but We've got issue, because we have jira.

La requête #463924 - [JIRA] Commented: (JRA-1549) Ability to rename a user a été crée.

Pour effectuer un suivi, et/ou ajouter un commentaire, veuilliez répondre à ce courriel.
Cette requête sera traitée dès que possible.

Merci de votre collaboration, Your request 463924 - [JIRA] Commented: (JRA-1549) Ability to rename a user has been created.

For a follow-up, and/or add comments, please reply to this e-mail.
This request will be treated as soon as possible.

Thank you for your cooperation,

Votre requête / Your request
Issue (View Online/jira.atlassian.com/browse/JRA-1549>)

Key: JRA-1549/jira.atlassian.com/browse/JRA-1549>
Issue Type: http://jira.atlassian.com/images/icons/improvement.gif /jira.atlassian.com/browse/JRA-1549> Improvement
Status: http://jira.atlassian.com/images/icons/status_open.gif Open
Priority: http://jira.atlassian.com/images/icons/priority_major.gif Major
Assignee: Unassigned
Reporter: Michael Phillimore-Brown/jira.atlassian.com/secure/ViewProfile.jspa?name=firewater>
Votes: 381

Operations
http://jira.atlassian.com/images/icons/bullet_creme.gif View all/jira.atlassian.com/browse/JRA-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel>
http://jira.atlassian.com/images/icons/bullet_creme.gif View comments/jira.atlassian.com/browse/JRA-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel>
http://jira.atlassian.com/images/icons/bullet_creme.gif View history/jira.atlassian.com/browse/JRA-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:changehistory-tabpanel>

Ability to rename a user/jira.atlassian.com/browse/JRA-1549>
Updated: 22/Apr/10 7:34 AM Created: 08/Apr/03 7:57 AM

The following comment has been added to this issue: [ Permalink/jira.atlassian.com/browse/JRA-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=192415#action_192415> ]
Author: Oleg Chekan/jira.atlassian.com/secure/ViewProfile.jspa?name=oleg.chekan>
Date: 22/Apr/10 7:34 AM
Comment:

this issue became more important now since you introduce Google Apps Integration.
It is a headache for JIRA administrators to recreate users with matching Google Apps usernames!

Project: JIRA/jira.atlassian.com/browse/JRA>
Components: Administration
Affects Versions: 2.0.2
Attachments: jira_renameuser_all.sql, OracleDB-UserNameUpdate-SQL-Jira3.13.4-Enterprise.txt, renameuser.sql

Description

As Jira starts to take off, invariably people play around with the system and begin to use it in anger gradually. During this time they sometimes find that the original username they created is not really the best they could have chosen. However, at the moment they cannot change this.

Would it be possible to change your login id as part of your profile? I know this is often a tough thing to do, but many of our users would find it useful.

Cheers!

This message was automatically generated by Atlassian JIRA/www.atlassian.com/c/JIRA/10140> Enterprise Edition, Version: 4.1.1-522 - Bug/feature request/jira.atlassian.com/default.jsp?clicked=footer>.
If you think it was sent incorrectly, contact one of this server's administrators/jira.atlassian.com/secure/Administrators.jspa>.

this issue became more important now since you introduce Google Apps Integration.
It is a headache for JIRA administrators to recreate users with matching Google Apps usernames!

Another point release for JIRA. Still no progress?

Does the renaming of the user differ greatly between databases? (I mean to say, the user mapping). Looking at how the user is mapped will give a clue to how to replace the user object instance across DB implementations (SQL Server 2005, SQL Server 2008, MySQL, PostgreSQL, Oracle, HSQLDB). I would do a back trace of how the user object is defined and then reverse engineer all the places the user touched.

well, the silence has been broken at last. we certainly won't buy any more atlassian products or renew until the issues have been properly fixed. Atlassian, this issue has cost you in tangible cold hard cash as well as intangible reputation.
That said, a proper fix not a rushed bodge please! And you know, provided the migration tools work 100%, I don't actually care about reverse compatibility.

-

Thanks for the updates. Glad somebody from Atlassian gave us some
updates here. There are lot of places in this bug where some SQL gurus
have shared some good SQL queries for making this change. Like
Confluence, why not Atlassian look into these queries for JIRA and
make them official?

Edwin, can you please updates us on this workaround part? Please note,
majority of folks are against big fat XML backup/restore option.

Thanks,
Amar

On Mar 14, 2010, at 8:56 PM, "Edwin Wong [Atlassian] (JIRA)" <jira@atlassian.com

Not being able to fix it is one thing, adding usernames to additional tables and not being to document it in a proper way is another. Are you trying to tell me that it would take fundamental work to tell us which tables we might stumble over a user in? I am not talking about custom fields, but tables created by Atlassian during development..

2+ cudos for an atlassian comment, after a very long silence.

Hi guys,

A quick update on this issue. We completely understand that inability for JIRA to change username is a major hassle for you.

Like a few other issues around user management, this is one that we do wish to fix. Unfortunately, as has been commented on before, making a change like this requires significant work behind the scenes.

The good news is that we are already at work in improving our user management infrastructure, starting with JRA-1962 (LDAP). Once that work is done, then the product will be in a much better position to tackle this issue. Realistically though, this issue (ability to rename users) will not be delivered in at least the next 6 months.

Unfortunately, I cannot provide you with any more detailed updates at this point in time apart from this. This issue continues to be on our radar during planning, and we will provide more updates when we know more.

Regards,
Edwin Wong
JIRA Product Management

If you have greenhopper your context wont be updated also and the saved config unless some other data is changed (example propertytext for the saved config etc)

So really it need to be analysed by atlassian and at least they could post us the SQL to do it safely without analysing everything ourself.

Martin Poirier
Ubisoft Montreal

Atlassian Support,

Can anybody please update on this? We all are not sure what our next should be here as we don’t have an ETA for this basic missing feature.

PLEASE RESPOND AND GIVE US AN UPDATE **ASAP**

Thanks,
Amar
Autodesk Inc.

I am in the process of evaluating enterprise workflow management applications & JIRA has found its way to the top of my list. However, seeing this issue not addressed for over 6 years is a rather large turn-off. I've discovered comments insinuating that the issue does not affect enough users to be worth fixing, but I completely disagree. As a potential admin of this application, this issue concerns me because I'm convinced that it will eventually result in downtime for my users.

First of all, user names will change. It happens with regularity.
Atlassian is expecting us to handle this behind the scenes with an export, search & replace, import. Ummmm... does this not result in downtime that will affect EVERY USER OF SYSTEM? It's not like I can wait to rename a user, either. If we're going to use LDAP authentication, that user name is going to change in a timely manner on all other systems on our network.

I've heard about direct SQL update scripting.
The problem here is that with each new release of JIRA, some of the DB tables are going to change... With many workflow customizations I intend to make, some of the DB tables are going to change. So, any scripted solution I may come up with could be obsoleted with any enhancement/update I roll out. Am I to test & maintain a user rename script with every enhancement?

This is a 'feature' that is so fundamental to any application which controls user access that I wouldn't have bothered researching had I not seen it as an open issue. I'm glad I did though, as it greatly impacts my perception of JIRA as a mature product. Workarounds for basic functionality hanging around for 6 years tells me Atlassian isn't ready to put money into staying at the top of this market. Maybe Rational Team Concert will creep up and earn that honor after all. I can't tell you how disappointing that is.

This is funny.. http://www.ptxstore.com/atlassian/index.php?cPath=30

I think every customer that does Atlassian's work by reverse-engineering their applications should get a free tshirt as a "Sorry we could not help you with your problem but fortunately you solved it yourself"-gift. I especially love the "Jira - Because you got issues" but i would never pay for it.

This weekend i am changing upn's of all 600 users for Jira, Confluence and Crucible. It is a task that have taken a fair 3 months in scripting, testing and feeling secure with, to the level i feel secure in doing such a major change without proper support. I once more want to stretch the fact that this is something that i would like to have seen in ANY product labeled or charged for as a "Enterprise"-solution. Once more, shame on you guys.. The only thing we as customers are demanding are that every time you release a new major or minor update (and add a handful of tables containing the usernames) is to includ a few SQL scripts that could help us out instead of turning your back on the organizations that made you what you are today..

Amen

Jonas Andersson

From what I can tell, no one from Atlassian has commented on this issue since 2006. That's not a good look.

This is not an academic or architectural-elegance issue: it directly impacts on all our staff as we use JIRA for in-house workflows well beyond software projects, e.g., the staff induction process. (We also use Confluence for our intranet but at least the workaround for changing usernames in that system is not quite so bad.)

I haven't read the whole comment thread but I presume someone mentions somewhere the basic case where users get married or divorced and their username in the rest of their IT world (starting with the main network directory) can be easily changed to match their new name in the real world. This makes sysadmins' lives easier because many tools list users alphabetically by username and we have a username convention that is <familyname><initials>, e.g., bloggsjf so they can easily find the user they're looking for when needing to do something useful for the user.

(Yes, I have now voted for this issue and the Confluence one.)

This is a really basic bug. It causes many problems, e.g. we can't implement SingleSignOn (with kerberos), cause there is no plugin available using Crowd-Alias-Feature (which we unfortunately need cause of this bug).
We would like to get the status and estimated fix time, too.

Hi,

Can somebody from Atlassian at least please give us a status on where this bug is at? Is it ever considered during any new release?

Thanks,
Amar

The problem is exacerbated in our environment, where externally we protect access to Jira via http authentication. Our user whose name changed
simply did not change username in jira, but did everyplace else. This makes jira inaccessible when mixed with http authentication, because it must use
the username passed in the header, set by apache's mod_auth.

Really, this is such a basic issue - allowing you to change your username, it should be escalated and fixed!

Thanks, every improvement/idea is welcome, but i didnt get the fullname-idea, the fullname isnt unique and can even be changed by the user himself. Such a intermediate solution with a binding attribute would not clarify things up either.
I would already be happy if i could search by the "bad username" in the user browser (currently only email works :/)
This issue is raised 7 years ago and workarounds have been given. I guess we can wait some more days for confluence 4.0 were such things get thought over indepth. At least thats what most people of a Major Release expect, i guess.
cheers
Frank

We're having the same issue at our office with a JIRA / AD integration project. The user accounts don't align and that's a pain for our users.

An alternate way for Atlassian to tackle this problem may be to leave the username column as the foreign key, and stop using it as part of user authentication. Atlassian can add a new editable "user login identifier" attribute on the User entity that is used for authentication. Poplists and user filters already use the user's full name on screen. The internal jira fk username would be nearly invisible to regular users.

Atlassian could decide on creation of new users whether to use the newly supplied "user login identifier" as the default value for the old fk username field, or start using a sequence number.

Just a thought,
Chris

Actually Amir, this was first requested in 2003! I think you are looking at the date field wrong

I like to add a "me too" to this issue, I vote for it and also I'm watching.
It's not a routine need for every admin but in Enterprise level from both view, when you have too many users and heavy uses and also whan you have other Atlassian product, it becomes major need. Especially in our case that we user Crowd too and different username for same person in apps seems like pain in the neck when integration time comes.
It's strange that this issue started in 2008 and know is 2010 and it seems popular issue when you review comments, voters, and watchers but yet is not assigned and scheduled!
BTW thanks Atlassian for the magic you bring to our world by your unique products.

The username within the changeitem-table is dropped into the value-fields (fullname goes to the string-columns). It is therefore not really necessary to check both.

And it really depends what type of usernames you have, i wouldnt recommend generally to update the customfieldvalue-table. at least at our site a label admin and a username admin shouldnt be renamed, that would only be helpfull if the label was meant for the user .

But it is calming that except for some small interpretations for user-environment-specific solutions the scripts (e.g. to the 3.13 MySql-one) are almost the same, so we shouldnt have left to much.

thanks for sharing
Frank

In Oracle DB, there are some CLOB (character large object) columns used and these are not included in the script.
(They need to be updated in another, more complicated way than usual VARCHAR columns)

CLOBs have been used for instance in the changeitem table. But since the changeitem table only contains
history data, I did not bother to update that.

Thanks Srini for updating the scripts to the newer version.

BR,
Peter

I ran script in our JIRA 4.0.1 environment, seems to work great. What do you mean with:

"(should also be made for the oldvalue clob and also for other field-types, like reporter etc)
Anyway, I did not update them, since they only contain history data."

Anyway, atlassian please provide an official solution. I always have a bad feeling with such scripts (to miss some fields e.g.).

Thanks so much for sharing Srini\Peter. I will be doing this upgrade on JIRA 4.0 so if I add new queries to this list, will share in this thread. Atlassian Support, sounds like this change username JIRA thread will continue to run on such workarounds In fact why not just mark it as WON'T FIX unless you guys have an exact estimate!

These scripts are for Oracle DB.

I should thank Peter (http://jira.atlassian.com/browse/JRA-1549?focusedCommentId=79599&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_79599) here for the SQL scripts. I had to introduce few tables for my version of Jira 3.13.4

-Srini

Thanks Srini. That would be awesome if you can share.

I will be out of the office until December 14th. Please contact Bhagat Nainani or Eduardo Rubio for any urgent issue.

Regards
–
Estaré fuera de la oficina hasta el 14 de Diciembre. Por favor contactarse con Bhagat Nainani o Eduardo Rubio por asuntos urgentes.

Muchas gracias