The key is jira and most atlassian products are feature mountains to be sold to upper management, but I can think of no end-user person that likes to deal with it on a daily basis. Then someone in the vein of slack or Asana comes around and eats atlassians lunch because they’ve neglected making the product good for anyone other than executives.

1) End users are not the buyer. It's the Head of Delivery, Iteration Managers, Agile Consultants etc that are. For them JIRA is great because it's heavily customisable and scales across the enterprise. It's actually quite hard to balance this with a great end user experience.

2) They are in the middle of a complete UI rewrite and I've only briefly used it but it's definitely much better than the previous versions. I imagine the Trello acquisition is also going to help them here.

I actually use Jira, Bitbucket and Confluence (all Server versiob) in a small team (maybe 5 people) and I really enjoy it. It‘s good in what it does, it does the things you want it to do and the 3 tools are good integrated.

For my other team members, they enjoy Confluence more than Jira, because Jira feels a bit difficult.

We have a gigabit connection but that doesnt make the site any faster. Not sure how much is being cached or what the bottleneck is...but there is something seriously wrong with the site's performance. It has become so slow I honestly think performance is the cause of fewer and fewer Jira tickets at work (people used to make tickets for tiny isolated updates to track them finely, but now it all gets shoved into the commit-of-the-day) and fewer updates/comments. People seem to interact with it only on sprint ends when they must do.

Well, they have succeeded in turning my entire team off JIRA. We basically don't use it anymore, mostly because their A B Z priorities didn't include making it not feel painful to use.

It's crazy to me when I can't type in JIRA... or when I drag a ticket to a new column, and it just doesn't go, and I reload and it's still in the old column. Or when I try to click a ticket and it just doesn't open.

The not being able to type fluidly has to be the worst though.

Our team has as well at least brought up the idea of potentially trying other products.

Some of it's probably me not really wanting to get involved with JIRA in the first place (who wants to manage tickets), but in the interest of being a better employee I've been trying to make sure I'm squaring out my work properly for tracking, etc.

And there's certain things, that I'm sure are there, but I just can't find sometimes. Like... how to add an epic easily. There's at least three different views for each ticket (when you create it, when you click it open into the modal, and the full screen view), and things are apparently in different places on those different views?

I'll take some of the blame, but it's a mess.

You’ve used enterprise products before right? Making it painful to use is basically priority number one.

Don't forget,

c) Pushing folks to their cloud offering, partly by

d) doubling the cost of on-prem.

The surprise price bump really pissed off people here; that, combined with doubts about their long-term commitment to on-prem put evaluating alternatives on the list for next year.

Being a tool no one loves is a bad place to start changing a bunch of stuff at once.

About that b). It‘s less about internet speed and more about your CPU not being fast enough to render everyhting in a useful time. With all that lazy loading, the browser is stuck with rendering for a couple of seconds - for each page...

This is why the browser isn't the best place for things like this. A Fat client is better. I still don't understand the push for webapps, when we have all this hp, storage is cheap, and we have modern installers that don't splat everywhere.

The browser is perfectly capable of stuff like project management workflow apps when you’re not shipping 22MB of useless abstraction layers in a runtime language.