If I was in Atlassian's situation this would be the last thing to focus on.
a) This is the biggest ever rewrite of their most important products. In this situation maintaining feature set compatibility is always going to be priority A, B to Z.
b) Their paying customers are mostly in the enterprise space who have very fast internet and stable environments i.e. payloads are quickly cached.
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.
For my other team members, they enjoy Confluence more than Jira, because Jira feels a bit difficult.
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.
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.