$6.8 million profit last year and an initial valuation for the company of $4.38 billion. It truly is a crazy world we are living in.
I was tempted to take a long position in Atlassian, but frankly I think the chosen price grossly overvalues them.
For the record, I'm still a big fan of the Atlassian suite, and also had thought about taking a long position once they were public, but I can't do it given the above conditions and this seemingly inflated price.
I'm just an onlooker but I've seen Jira (the proper tool for a problem) was universally shunned by management because they specifically didn't want to be tied into the rest of the Atlasssian ecosystem.
I realise that it makes no sense, but it's partly because they want diversity rather than being strung over a barrel by one vendor, and partly because they are ordered to use some different components by the higher-up conglomerate managers; which is what Enterprise is all about.
I don't know what the integration options were with other systems but management struck it off the list from the get-go regardless. We were already using it internally successfully; but hey no let's try to shoehorn ServiceNow to do the same thing.
I'll leave the rest for your imagination.
Yes though, it sucks for us on the ground floor. We really don't give a crap WHAT gets used as long as it works, and all the different crappy products with zero integration absolutely doesn't work. Tell that to management though; they don't have to use it.
I'm guessing the fact that IRC is used is that it's reliable, simple to set up, and works for a rather large audience even without any redundancy. Most extra functionality that the Slack etc. provide – integrations, notifications embedding things – are not really necessary (but possibly wanted) in that context. E-mail still reigns supreme for anything that can't fit in simple text, and certainly for more formal comms and sign-offs.
Look, I didn't say management was smart. That's just the dumb way they look at it.
Before that we had a poor mediawiki install, and for task management basically nothing (or rather, awkward internal tool compatible with IE6...).
It is a blessing.
I guess if you have been using (and abusing) Atlassian tools for years, you will experience some tool fatigue, which is natural.
Gosh, I'm 63, and I talk about JIRA like that!
It become a problem when a PM gets his hands on it, included about 50 steps with manual approvals etc.
There's arguments to be made on both sides, and there's never just one answer. Default JIRA flow for some people is probably a godsend compared to what they're coming from, and yes, for other operations, having it mimic what's already in place probably needs to be done.
I actually joined the company just as they were about to move to Redmine, and recommended Jira instead after playing around with the Redmine test instance for a while. They were worried about the cost though, and I didn't have much say yet, but in the end switching to Redmine was the best argument for getting Jira. I didn't even have to push for it - after a few months my manager came to me and said he'd already got the funds approved!
Last few years we use Redmine mostly. In the beginning I had mixed feelings about it. Now I'm OK with it.
We sometimes need to switch to Jira in our projects. It's always a pain nowadays. I used to love Jira time reports, now I just don't get them.
My perspective: Redmine covers the basics we need, don't have the feature creep problem and does reporting (time reporting) really really well.
Rant mode continued: In several projects we use YouTrack [0]. Initially I was very excited: e.g. great UX etc .. But! It's time reporting capabilities are just rudimentary.
In the end we do the following: created internal tool too fetch time reports from different systems and to push to our Redmine system (via REST API). Redmine serves our reporting needs well. Still, in some extreme cases also use excel via ODBC..