Sounds kinda like the users fault, having a corporate and personal email on the same account. Atlassian probably could put a warning though about the issues that could arise.
I was notified about the Apr 14 deadline by trello twice on both my personal (not connected to org in any way) and work email:
- on Jan, 30;
- on Feb, 29.
As much as I hate Atlassian for their other products this seems like a responsible timeline for such kind of change.
While I understand, the pain - I sympathize: please note that no permissions management system (or identity and authentication is so perfect that every case can be handled perfectly). As others say, you should have verified spent a bit of time to cleanup - because at the end - you lose time/money/whatever.
In the worst case, any company or even govt can just say sorry or some credits.
Even if the company is to blame 99 % you need to take 1 % responsibility.
But you created the problem in the first place by adding your work email to an account that had your personal boards in it. By doing that you gave your employer a means of controlling that account. You basically planted a time bomb that could go off at some unpredictable time in the future. And it went off.
Depending on the jurisdiction, if one suffers money damages as a result of the unapproved transfer Trello or its business clients may be exposed to liability. Also, I imagine there may be privacy or consumer protection laws that could apply too even in the absence of money damages.
HE didn't “plant a time bomb”; Atlassian ripped him off, plain and simple.
(Oh, sure, you could argue that he “planted a time bomb” by giving Atlassian the means — that email address — to rip him off... But please don't. That would be like arguing that a rape victim “planted a time bomb” be dressing too provocatively.)
See: Github - where you can SSO into your organization's repositories but this is completely separate from your personal repositories.