Slashdot Mirror
Atlassian Acquires Trello For $425M (techcrunch.com)
An anonymous reader shares a TechCrunch report: Atlassian today announced that it has acquired project management service Trello for $425 million. The vast majority of the transaction is in cash ($360 million), with the remainder being paid out in restricted shares and options. The acquisition is expected to close before March 31, 2017. This marks Atlassian's 18th acquisition and, as Atlassian president Jay Simons noted, it is also the largest. Just like with many of Atlassian's other acquisitions, the company plans to keep both the Trello service and brand alive and current users shouldn't see any immediate changes.
And still have no idea what these companies produce or why I should care.
Only the State obtains its revenue by coercion. - Murray Rothbard
I bet the layer of product managers at Atlassian became top-heavy, with number of managers outpacing the number of sub-par software products they release (like JIRA.) So, the natural next step in the evolution of the company is to buy a non-sub-par software product company, and let the product managers have their way with turning the purchased software products into sub-par products. That way, every product manager gets a fair share of practice at screwing up perfectly fine software that probably doesn't really need to be modified in the ways they are intending.
I also have no clue, better raise a ticket!
JIRA has a kanban board and it's pretty awesome. It's been a little while since i've used it but I remember the columns had to be defined by issue filters instead of just an arbitrary name like in Trello and having to use filters to define columns was a bit of a PITA. If you take the time to really master JIRA it's an incredible tool where Trello lets you get all the advantages of kanban with the least amount of effort. I suspect you'll be able to create issues in JIRA and have them show up in Trello pretty soon (if not already) long term I see Trello as a stepping stone to JIRA. I describe them to non-technical folks as Trello when you need a good pickup truck and JIRA when you need an 18 wheeler.
I came to the datacenter drunk with a fake ID, don't you want to be just like me?
Atlassian guys probably bought it because they were sick and tired using their own crap.
sudo rm -r -f --no-preserve-root /
Those are exactly the sorts of things that people say and believe just before a bubble bursts!
Thank you for expressing them. You've given the rest of us hope that the end of all of this "Web 2.0" nonsense is closer than ever.
I agree that most of Atlassian's stuff is overpriced bloated crap, but comparing JIRA and Bugzilla is like comparing dial-up and FIOS and claiming they're both internet access from your phone company, so they're the same.
We looked at and rejected Confluence because MediaWiki is free, less resource intensive, and works. We rejected Bamboo because we find Quickbuild (another commercial product) is cheaper, less resource intensive, and much easier to use than Bamboo or Jenkins. Commercial packagings of OpenSource VCS systems like SVN or Git give me hives, and I won't touch them.
But... Especially when you need your ticketing system used by non-programmers, JIRA beats out Bugzilla in user friendliness, workflow tracking, and a bunch of other important features. It's not even a contest. We tried both Bugzilla and TRAC, but JIRA won hands down in terms of user acceptance. That's probably the most important metric there is for a ticketing system.
much less productive than Bugzilla
I'd much rather see something like redmine raised as an example. Bugzilla is a terrible ticketing system. If JIRA is worse than that, that just seems like an extremely hellish proposition.
First they talk people into getting rid of Git then shove Bitbucket down your throat.
I assume you are talking about something else than getting rid of Git, since bitbucket is a git based solution. I prefer GitLab over bitbucket for on-prem, and github for community based work (networking effect and all).
What we have found to work best for us has been:
redmine - bugs/feature/project tracking
gitlab - repository and code review (I know, there are better code review systems out there, but we don't have fancy needs)
jenkins for CI - again nothing particularly sexy there to really feel strongly about one way or another
mattermost - team chat for larger teams that warrant that - benefits of slack without the drawbacks
XML is like violence. If it doesn't solve the problem, use more.
Easy, let's say facebook has 1 billion users and each user is worth 5$ of marketing potential, facebook is now worth 5 billion dollars - get it?
You can't go down to the piggly wiggly and spend marketing potential.
But you can go to a bank and your investors, wave your "marketing potential" about, and then get some sum of {loan, stock, approval to spend some cash} to BUY the Piggly Wiggly outright for $100 million. You end up increasing your "marketing potential" by $200 million because of "synergy", the news of the buyout boosting the value of Piggly Wiggly, etc.
When the bank wants their loan money or your investors point to the plateauing stock price, you simply repeat the process with a new target. When you run out of targets you "spin off" prior targets into their own entities and sell their shriveled husks to some chump. If you can't find a chump, you cut the staff, burn it to the ground, and sell the IP and assets for pennies on the dollar.
If this goes on for a while, you'll end up posting successive quarters of losses and people will be calling for your head. Just jump out the window with your golden parachute and move on to the next company to repeat the process.
I don't know what Atlassian will do with Trello, but their existing products are horrid.
We use JIRA (a bug tracker) and Confluence (a wiki). These suffer from
- poor use of screen space
- useless search
- crude and inconsistent text editing
- verbose, non-standard, and broken markdown
Atlassian products are built for shelf-appeal: they are designed to look good in sales demos, and to appeal the people who sign POs and checks: CEOs, VPs, and directors. But they don't actually work for the people who have to use them: programmers and first-line managers.
Atlassian puts their own bug database online. When you find a problem with Atlassian software you can search for it there. You will likely find that other people have found this problem before you, and opened tickets on it, which Atlassian has since closed, explaining either
- yes, it is broken, but fixing it would be hard, so we're not going to
OR
- no, that's the way it is supposed to work, and we're not going to change it