search

fuzan / rietveld

Automatically exported from code.google.com/p/rietveld
Apache License 2.0
0 stars 0 forks source link

Migration does not free up old username #442

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Use Rietveld.
2. Change your Google Account primary address (such as by signing up for Gmail).
3. Observe that Rietveld assigns you a new nickname.
4. Use the migration facility to claim your old issues.
5. Attempt to change your nickname to your old nickname.

What is the expected output? What do you see instead?

I expect migration to free up the nickname so I can continue using it under my 
new email address. Instead it is still “in use”.

What browser are you using?  What version? On what operating system?
Chrome 27.0.1453.56 Mac OS X

At what URL are you accessing Rietveld?  (e.g. codereview.appspot.com)
Please note if you are using the Google Apps Labs version (e.g.
codereview.<yourdomain>).
https://codereview.appspot.com/settings

*** If you are a Google employee please say so or mail rietveld-admins@
directly. ***
Yes, but this issue applies to my non-corporate account.

Please provide any additional information below.
This is a follow-up to issue 201.

Original issue reported on code.google.com by kpreid.switchb.org on 30 Apr 2013 at 4:47

GoogleCodeExporter commented 9 years ago 
Can't you log in with your previous account and free the nickname yourself? The 
migration task was just intended to migrate issues only.

Original comment by albrecht.andi on 4 May 2013 at 7:51

GoogleCodeExporter commented 9 years ago 
No, because there is no previous account — the email address in question has 
become a secondary address for my sole account. (This is what happens 
automatically to users who have signed up for Gmail, which was the original 
motivating scenario in issue 201.)

I suppose I could disassociate the secondary address with my Google Account, 
create a new account with that address, log in with it, etc. but I fear that 
that might have unexpected consequences, and in any case I don't think I should 
have to do that.

I say it should be part of the migration operation because migration was 
created to solve the 'new primary email' problem and this is the remaining part 
of that problem.

Original comment by kpreid.switchb.org on 4 May 2013 at 2:11

GoogleCodeExporter commented 9 years ago

Original comment by albrecht.andi on 5 May 2013 at 7:19