71–80 of 169 posts
Earlier quoted context omitted.
> There are loads of either commercial or open source issue trackers, wikis, combinations of both, etc. etc Yes, and they all suck. They go from a pain to use (Bugzilla) to a huge mountain of useless and worthless crap with a obscene price tag (Rational tools) It seems to me they are in the right path
> Yes, and they all suck. Redmine ain't bad.
It feels like the universe makes sense again.
Earlier quoted context omitted.
If you wanted to keep the company private and give the Vc's an exit you can always do a leveraged buyout. Basically borrow loads of money from a bank and use it buy back their equity.
doesn't that pit the management against the VC on pricing when doing a management initiated LBO?
This is a company that was founded in 2001. I still remember their CEO building his original audience on TheServerSide.com, back when Enterprise Java was the thing. They took 13 years to get to this point, a solid 8-9 years longer than most enterprise SaaS companies are expected to take (by VCs). And yet, not a single VC I've asked if they wish they were in Atlassian has said no. You can build huge companies on your…
Can you give examples of SaaS companies which did that in 4-5 years; I know you said 'by VCs', but i'm curious.
oblig. BitBucket has free private repo's https://www.atlassian.com/software/bitbucket/overview you don't get to 3 billion dollars without giving away a lot of stuff for free to infiltrate the enterprise
I use Github for personal stuff and Bitbucket at work. They're pretty comparable. I don't really have a problem with either. Some parts of the Bitbucket UI are nicer, some parts of the Github UI are nicer. It's hard to beat free private repos but note that they are limited to 5 users. If you have a larger team, you've got to pay.
Really cool that you can reach that kind of valuation with a basket of products, rather than a single run-away network effect fueled win. I find it very inspirational that they do that well by building great software that people love. also: They really make awesome products (we use BitBucket, HipChat and Confluence)
>great software that people love As someone who has to use and administer JIRA I'll have to respectfully disagree. The nicest thing I can say about the product is that it was built "by engineers, for engineers". People who want empowering software that gets out of the way appear to have been an afterthought.
In the real world, simplistic ticketing systems fail to meet enterprise needs, which are complex and peculiar, arising from weird contract clauses, irrational political outcomes, legacy processes etc etc. JIRA's multi-layered customisability is a huge boon in these environments.
Also, people aren't actually stupid. Yes, even non-engineers can use a complex piece of computer software! A little training goes a long way. Who knew?!
We've had a rough, shaky time using Jira, but it's almost entirely due to internal politics and constantly-shifting business priorities. (aka CEOs and owners who are just megaphones for their corporate customers) We intended to replace our invented-here ticketing system (which has Zendesk integration) with Jira, but instead we integrated Jira into that invented-here ticket system. On the other side, my team has been…
We had a similar bug that we worked around by adding a transition view of "Resolved Issue Screen" to all steps leading to done in the Add Workflow Transition page.
We've had a rough, shaky time using Jira, but it's almost entirely due to internal politics and constantly-shifting business priorities. (aka CEOs and owners who are just megaphones for their corporate customers) We intended to replace our invented-here ticketing system (which has Zendesk integration) with Jira, but instead we integrated Jira into that invented-here ticket system. On the other side, my team has been…
You can also bulk modify issues that are unresolved by transitioning them to "In Review" and bulk updating them again back to "Done" which then correctly set the resolution field. Unfortunately this technique means that all your issues are now resolved on the same day so your graphs etc show a big spike on one day.
For some reason this bug occurs after a few days with any of the default workflows in Jira, but it's not too big a deal if you spot it early and fix the workflow to resolve issues correctly.
As for the Jira/Godzilla thing, I always thought it was a reference to Mozillas Bugzilla, which I thought was kinda cool :)
Hope that helps!
> 1/3 of the top 100 are SaaS, but not all are purely enterprise.