mhp

I'm sorry it's confusing. It's trying to say that SAML SSO is provided via Atlassian Access - but you don't need to buy Enterprise to buy Atlassian Access - it's a totally separate product (and does not require Enterprise). We are in transition right now (formerly SSO was provided by Enterprise) and so our final pricing page isn't quite where it needs to be.

It's the other way around. You only need to buy Atlassian Access to get the SSO + enforced 2FA for your Trello (and also any other Atlassian product) users.

Trello Enterprise (optionally) would secure your content (i.e. attachment restrictions, power-up restrictions, token restrictions, audit logs, team management).

There is always more engineering work. The questions is does the app need to add new vocabulary type features to get there, or is the work focused on making the API more flexible for 3rd parties, or the signup process less onerous, or making exports take half the time they normally take. There's definitely a balance but they have to be seen as worthwhile and valuable goals instead of adding new words to the object model or new pages to the site. Typical product creation can sometimes be "can I make this thing possible?" instead of "should I make this thing possible or accept that this is not the job of this application". Of course you can make your app do anything you could possibly want... what should it do?

We've got some stuff up our sleeves...

The part that bothers me the most about this is that our app has all of the certifications and controls that they would need - they just don't know that. Soc2/3, ISOs, Fedramp, etc (trello.com/security). But as you point out, you have to get it approved and that requires navigating a lot of internal roadblocks.

Thanks for taking the time to say that. One of the most rewarding experiences of my role has been accepting thanks like yours, online and in person, on behalf of the team that actually built the product. We owe all of our success to your recommendations and referrals.

Hi! Co-founder Trello here. Agree that “behind” is maybe weird here and probably not intentional but then again the whole Trello team is now part of Atlassian. Every day we are part of the group of people that are building the future products and features. Even without us, I think today’s launch shows Atlassian is heavily invested in “unleashing the potential of EVERY team” (emphasis mine) and their design and understanding of how to do that is evolving. If you love the Trello UX then my guess is you are going to be pleasantly surprised about where we go in the future.

omg, I'm going to have a boss! I'll be working at Atlassian. Lots of stuff to still do in the future to reach our (and my) goals. And now we're going to have a lot more fuel for our engines to get there.

Thank you for the kind words.

I promise you Atlassian understands why Trello is so successful. You described Trello's core strength perfectly - and this one of the reasons they are committed to keeping it as a standalone service.

(disclaimer: I'm the CEO of Trello)

Our vision is that it gives a group of people a shared perspective. It puts you on the same page. That could be your fiancé and your mother-in-law planning your wedding or it could be your HR team trying to structure your employee onboarding process.

It's not a project management tool anymore than it is a bug tracker or a crm or an applicant tracking system. People use Trello for all of those things but at its core, it is just a list of lists.

The power comes from understanding how that metaphor can help provide structure to some process that you have. (Trello comes from "trellis" - a structure to help plants grow).

Check out trello.com/inspiration for some examples. It's a bit like explaining to someone what a spreadsheet is before they have seen one and why they would use one. Once you grok it, it's very powerful.

Nope. No ads.

Quantcast has our mobile data too.