Scenario:
Corporate policy changes internal email id of all contractors to a qualifie one, eg
from: joebloggs@corporation.com
to: joebloggs@contractor.corporation.com
Without handover period, the original email is closed down and cant receive.
Unfortunately for Joe, he cannot remember his password.
Worried his project involvement is quite complex, and if he was created as a new user a lot of admin would be involved, he comes to jira admin for help.
- Can jira admin reset his password, as any time he tries he wont get the reset password email?
- Can jira admin reset his email address, as this would let him just continue
- if all else fails, can jira admin migrate all his open and closed tickets over to a new account created with his new email address.
Admin thinks about it (sic), sees a storm coming, he isnt the only contractor.
Atlassian, we have a problem, and therefore you have a problem...
We dont have control over corporate email policy, and we can't anymore reset a users password, and when I try using api/2/user?username=joebloggs
{emailaddress:"joebloggs@contractor.corporation.com}
I get internal server error...
How do I handle both this individual situation, and the bigger mass migration to the new email address format?
I get