5 ms·

This sucks but isn't Atlassians fault. The lesson is of course to never connect an account you don't own to anything you can't afford to lose.

• jaimex2 7y ago
  Curious how this isn't Atlassians fault. Can you elaborate?
  • hashkb 7y ago
    User should have removed work account from valuable personal account immediately after leaving job.
    • deleted 7y ago
      [deleted]
    • CRConrad 7y ago
      Sure. But he forgot. That's not a reason to give the company, with which he is no longer affiliated and to whose boards he hasn't had access for years, ownership of his personal account and all its boards.
  • dvhh 7y ago
    Going on a stretch here, but assuming that the user also use the company email for SSO, means that company (paying client) trade secret were potentially in some of the trello board the user was using. Considering that it would be an invasion of privacy and confidentiality for Atlassian to access the content of the board to assess which one is corporate and which one is personal, Atlassian to the safer approach to satisfy a paying client. Consider that as a free user, with no advertising to monetize you, one could guess that Trello used you for advetising (Unless you are a paying user for your personal account, that could change the story). Of course I am not big fan of the approach, because the user probably linked personnal and work account for convenience, and that trello probably didn't make it easy to make the switch between work and personal. On the other hand, how do you prove that an email address is a personal one ?
    • shashanktomar 7y ago
      I am the user in this case. When I linked the accounts almost 6-7 years ago, Trello was not part of Atlassian and there was no SSO in place. At some point, they introduced it, but still, the regular way of login was working. There was no notification from there side that it will stop working abruptly. The company email address in this case what @comany.com and the personal one was @gmail.com. This is how they handed over all the accounts ending with @company.com to my previous company.
      • dvhh 7y ago
        I understood you were the user, and that what Atlassian was way too cold and lazy on their part. but again, to play devil's advocate, Gmail do offer professional account part of the G Suite. Without knowing your work history, it would be difficult to know if the Gmail address is also not a "professional one". On another hand do you think notification would have solved the issue ? And wouldn't a more malicious employee just delete all the boards if they did not part with their previous company on good term. Obviously I don't know everything from the story. And my assertions are very far from the truth. I am trying to understand what would motivate such a decision (beside the obvious Atlassian is a heartless money-grabbing company that rot everything it touches)
        • shashanktomar 7y ago
          The ownership of the board is by account. In this case, all the company accounts were anyways invisible to me as my login email was personal gmail account and I only had the permissions to delete board owned under my account.
      • pdonis 7y ago
        > When I linked the accounts almost 6-7 years ago When you did this, was the Trello account used for just your work with that employer? Or for both work and your personal stuff? Or just your personal stuff? [Edit: I see from your response elsewhere in this discussion that it's the second of the options above. I'll respond further in that subthread.]
• shashanktomar 7y ago
  I understand Atlassian's part here. But Atlassian did this on purpose. They clearly understand the implication and the ownership of accounts, but they deliberately ignored individual users over big corporate accounts. And in my case, they didn't even have the courtesy to notify me in any way. I just stopped working one day leaving all my data unbale to use.
  • nerdbaggy 7y ago
    Why would they allow an account with multiple email addresses to login with the non SSO one? In your case you aren’t malicious but there could be used maliciously - add your person email - get fired and login with that email and now have all the data
    • jakelazaroff 7y ago
      Why not just prevent the user from accessing boards owned by the company?
    • toomuchtodo 7y ago
      I would argue that the "right" course of action is to immediately require human intervention when an SSO email is added to an account (or an existing account with an email address, such as a startup "going big league", becomes SSO managed), so that account ownership issues are resolved at that point in time by the parties with ownership interest, not Atlassian having to do so.
    • shashanktomar 7y ago
      The ownership of data is attached to the email. As soon as i left my workplace, none of the data created under my company account was visible to me. On top of that, they launched SSO support lately. It was not SSO when I connected my accounts years back.
    • itronitron 7y ago
      Why would they allow an account to have more than one email address?
  • 7y ago
• deleted 7y ago
  [deleted]