FYI that we're implementing read-ony mode in our data center product line, and we've also got various knowledge base articles for how to achieve this should you need it:
I have never had the opportunity to tell anyone at Atlassian how much I love Confluence. There are so many cool technical feats that improve my experience, like being able to open an embedded spreadsheet in Excel and having it update the version on the page when you hit save. So many things that aren't natural for the web are seamless, like indent levels and accepting pasted images. So many organizational tools like excerpts and child view macro. So many usability features like attachment versioning and keyboard shortcuts.
It takes a great company to make such a great product so easy to use. Thank you.
I'd love to hear more about the APIs we need to improve. We are exploring using GraphQL for our next revision of APIs, and your experience would help us with that effort. If you're interested - we'd appreciate your feedback.
I haven't touched it in over a year now, but you might want to look at Bamboo. That product seemed rather stale and there's plenty of +1'd issues/requests on your jira.
One exceptionally bad example I remember is returning HTML for certain 404s even though caller requested json. It was for missing artifacts among others IIRC.
Thanks for your comment! My apologies, no disrespect intended - I should have clarified I meant "left" for the purpose of your IPO. It was and is fantastic to see Australian talent prosper to such heights.
I see many clever companies where I live in Melbourne - however I am saddened by what I perceive as the neglect the government is showing for the tech sector, especially startups; I'm looking e.g. at how share options are taxed. I believe there's a lot of lost opportunity here.
Both founders still live in Australia. Roughly half our global staff are Australian.
These days with local VC funds you can get funding much easier than when we started. That said, for later rounds (>150m+ valuation, tens of millions of dollars in), you are likely to get a better deal from the USA firms.
In meeting with Michael, and discussing how we could work together, Michael could not be more clear that Trello's success is predicated on is breadth and its appeal to many different use-cases.
This is most clearly displayed in their inspiration page, that includes many, many use-cases:
https://trello.com/inspiration
Keeping this strength alive will be key to Trello's long-term success.
Hello, you received a reply in another comment about adding more time tracking and reporting to Trello.
This goes right to the core of all of the issues/conflicts bundled into this acquisition from UX details up through to target users and culture clash.
Time tracking is a manager-oriented feature, not a producer-oriented feature. The users producing the work usually resent things like fine grained time tracking and comparitive producer reporting because it distracts from actual work, treats creative or complex processes as though they are part of an assembly line, encourages micro-management, pits quality against time, and emphasizes wage servitude.
Managers can use Trello to stress out their employees too, but not to the extent that JIRA-ish tools enable.
The problem is you are selling to managers who love to micromanage their employees and have nothing better to do than fiddle with configuration, reports, or have meetings with the people they hired to do that.
This is why developers who are smart will probably try to protect themselves by pre-emptively replacing Trello with one of the dozens of free or inexpensive clones before you can start corporatizing it and their company.
Be it for the general use cases or for the software team collaboration, time tracking and reporting features are always useful. As a user of both JIRA & Trello, I hope Trello soon gets all the time tracking and reporting love that JIRA team could add. Congrats and good luck!
JIRA shines in areas that (a) have workflow and (b) require repeatable processes across a number of people.
Once you have 20+ people on a project, you need repeatable processes.
In cases like bug tracking, project management, customer service, help desks, HR onboarding and hundreds others you need workflow.
Trello shines in areas where you have (a) small teams or (b) require ad-hoc semi-structured data.
In small teams, even if repeatable process would help you, it's not worth the cost of setting up a system - you achieve it by social means.
Trello also has many, many use-cases where you want to start something quick, or personal. In this case it really shines, with near-zero friction to get started.
This. I hear a lot of whining about JIRA, which is fair since it's a huge pain to configure and learn all the quirks of, but usually it's overkill for those folks (perhaps myself included right now).
But the folks who have a working process and a large number of people and teams are usually complaining the other way round: that no tool supports their workflow. Which is where JIRA shines. I don't know another tool that can be configured to such ridiculous detail.
The Trello acquisition makes total sense because it fills in that gap that JIRA is bad at.
Whatever you do, just make sure you always keep a functional free tier. I can tell you that for for us, as far as Bitbucket and Trello is concerned, the free tier is what got us in before purchasing a plan several months later.
AWS applies the same trick with some startups in China (like they did with us) and I guess Silicon Valley as well. Bunch of free credits, free for a year. After you have your infrastructure with them it will be hard to switch to somebody else.
@farkas I know this is off topic - but whilst you are here can I ask you a question?
If we have built a product that is a (we think) great fit to the Atlassian customer base, who would we speak to in order to create a partnering arrangement with Atlassian? Does Atlassian do such business partnering arrangements?
It's not an addon for an Atlassian product so does not seem to fit to the Atlassian marketplace.
I'd encourage you to take a look again.