If I never have to hear about JIRA and Confluence again, it'll be too soon.
Atlassian is 20 years old and unprofitable
451–460 of 515 posts
Re: Atlassian is 20 years old and unprofitable
#452Somehow I'm not surprised. A few days ago[0] I was writing a Jira ticket after hitting the "Create" button and I wrote the description (the body of the ticket) for ~30 minutes. I switched the ticket type from A to B (no epics involved) and it wiped out the entire description. All I did was select a different item in a select drop down box provided by the form's UI. There was no warning it would clear the description…
I can understand your frustration, and there should be some warning, but this is not a bug.
Every issue type is configured with its associated issue-create screen and that screen has its fields. When you change the issue type during issue creation you're replacing one set of fields with another which results in the information loss you experienced. This just doesn't affect the description field, but all other system fields and custom fields.
Re: Atlassian is 20 years old and unprofitable
#453Somehow I'm not surprised. A few days ago[0] I was writing a Jira ticket after hitting the "Create" button and I wrote the description (the body of the ticket) for ~30 minutes. I switched the ticket type from A to B (no epics involved) and it wiped out the entire description. All I did was select a different item in a select drop down box provided by the form's UI. There was no warning it would clear the description…
Atlassian’s WYSIWYG editors are some of the buggiest bits of UI I’ve ever had the misfortune of using. Writing anything in Jira or Confluence is an exercise in misery. Even basic stuff like hyperlinks often go wrong.
Re: Atlassian is 20 years old and unprofitable
#454Earlier quoted context omitted.
It is just a ticketing system with a very robust business process engine. Most complaints I’ve heard about Jira boil down to the horrible processes people choose to implement in it.
Thats the rub too. Jira setup in a simple way is what most people need. Yet you get process people in there and suddenly you have 50+ fields to fill out before you can even start working on something. Then another 20+ fields to fill out to close out a ticket. I went from taking 2-3 hours total to plan out a sprint, to it taking 3-4 days and many meetings. And no one can tell me how these fields are used day to day, w…
The same thing happens to orgs using Salesforce, custom fields get added and ignored ad infinititum.
Re: Atlassian is 20 years old and unprofitable
#455Jira is becoming Microsoft Word in terms of just piling on the features. Atlassian needs to learn to say no sometimes.
Re: Atlassian is 20 years old and unprofitable
#456Earlier quoted context omitted.
Given their recent outage (that was this quarter right?) that is bonkers.
The outage was pretty bad but it only affected 0.4% of customers. Not surprising that it didn't materially impact revenue.
It didn't scare new customers away is what I find surprising. That outage lasted over a week and data was lost/inaccessible..
Re: Atlassian is 20 years old and unprofitable
#457Somehow I'm not surprised. A few days ago[0] I was writing a Jira ticket after hitting the "Create" button and I wrote the description (the body of the ticket) for ~30 minutes. I switched the ticket type from A to B (no epics involved) and it wiped out the entire description. All I did was select a different item in a select drop down box provided by the form's UI. There was no warning it would clear the description…
The problem with JIRA is that yes, everyone uses it, but most people hate it. In my experience, the only people that advocate for it are PM/PMO/TPM type people who need very specific and customizable workflows and reports. And even then, they continually run into quirks and bad UX everywhere.
This leaves them very vulnerable to another company taking their market share, as soon as they create something better that is extensible enough to get management signoff. I know a lot of companies have tried and failed here, but someone's going to eventually do it.
Re: Atlassian is 20 years old and unprofitable
#458Earlier quoted context omitted.
The idea that growth is better than profits was in-built into Atlassian's proposition to shareholders, ultimately. The slow and steady mentality is fine, but we see over and over that it isn't what the market wants. A private company or a high risk growth company, those are the two options for a software company. Either that or they'll be taken over. They're revenue now is just a $2bn, so that "grow grow" mindset fro…
> revenue now is just a $2bn "only" $2bn ? this is bizarre to see discussed without question
It makes perfect sense when we’re talking about a public company. It would be a completely different conversation if they were private.
Re: Atlassian is 20 years old and unprofitable
#459No post body was provided.
Re: Atlassian is 20 years old and unprofitable
#460Earlier quoted context omitted.
The problem is that choosing to be unprofitable is a strategy that maybe worked (or just was fashionable) the past decade under very specific circumstances (lot of free money chasing higher returns in a context of very low rates), but otherwise obviously makes no sense, it's antithetic to the very idea of a business. It's not to be confused with the sane version that is reinvesting profits for growth instead of distr…
In the space Atlassian is in, choosing to be unprofitable while quickly growing could make sense. It is not necessarily true for other sectors (e-scooters, different delivery services, maybe even Uber), as there is no stickiness in those areas. Whenever a cheaper Uber would come to my city, I'd drop them within a second. They are usually cheap while they can burn VC money. If Atlassian can keep their system for a cou…
If you are actually producing e-scooters it could make sense as well when you have plans for reducing your costs long term through economy of scale so you reach the minimum efficient scale.