Corporate policy changes internal email id of all contractors to a qualifie one, eg
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.
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
I get internal server error...
How do I handle both this individual situation, and the bigger mass migration to the new email address format?
Hello, Community! My name is Gosia and I'm a Product Manager on Jira Server and Data Center here at Atlassian. Since 2002 when we launched our public issue tracker, jira.atlass...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs