Subject: Severe UX Issues Following Layout Changes – Evaluation of Alternative Platforms Underway Dear Atlassian Team, We would like to inform you that the recent switch to the new Jira and Confluence layout, along with the current user experience (UX) interface, represents a serious disruption for our company. The new design is not only confusing for our team, but it also significantly impairs our daily workflow. The changes are so drastic and detrimental that they effectively amount to a provider switch – as our previously efficient way of working is no longer feasible. We are therefore currently in contact with several alternative providers, including: * Microsoft 365 / Teams / Planner / SharePoint * Asana * Monday.com According to community feedback and user experience reports, these platforms offer a noticeably better experience in many areas and receive significantly higher ratings on review platforms such as Trustpilot, G2, and Capterra compared to Atlassian. We kindly ask for a statement on whether and when a return to a more user-friendly interface – or at the very least, a real choice for existing customers – can be expected. Otherwise, we will be forced to pursue a transition to one of the above-mentioned alternatives and document this step publicly on relevant review platforms. Best regards

Dear Marc, Thank you for your reply – however, I must express that your response is, quite frankly, disrespectful to paying customers and unworthy of a professional discussion. Your message completely ignores the scale and substance of the concerns raised. You dismiss a comprehensive, constructive critique with a casual “you are free to switch platforms”, while failing to acknowledge the real impact this forced UX transition is having across teams worldwide. Your tone implies that user frustration is optional – it is not. Let me reiterate and clarify why this is not just a “matter of taste”: * There is no opt-out – Users are being forced into a new UX without choice, which contradicts standard enterprise-grade software practices. * Overloaded interface – Excessive icons, inconsistent spacing, and unclear design language now dominate the screen. * Key functions are harder to access – Basic workflows are now buried in unintuitive navigation paths. * Poor readability – Text elements clash with layout spacing, damaging clarity and reducing productivity. * Increased click depth – Simple actions now require far more effort and time than before. Browser performance issues – Many users report severe lags, crashes, or inefficient rendering – particularly in long Confluence pages or complex Jira boards. * Browser inconsistency – UX behaves differently in Chrome, Firefox, and Safari – sometimes with broken or missing elements. * Navigation is confusing – Jira’s new layout makes it harder to switch between Epics, Backlogs, and Sprints without losing context. * Mobile usage is worse than ever – The new design is barely usable on tablets or phones. * No real benefit – The changes are cosmetic at best and degrade usability without offering any functional improvement. Your comment did not address any of these points – and worse, it signals that Atlassian is not listening to its user base. Dismissing valid criticism as “free to switch platforms” is not only arrogant but strategically shortsighted. What you seem to miss is that this is not a minor adjustment. A significant share of experienced users is reaching a breaking point – and the shitstorm is already brewing. Just check the trending feedback on Trustpilot, Reddit, LinkedIn, or even within this very community forum. We do not need flippant remarks. We need accountability and – at the very least – a roadmap toward an optional UX toggle, or an official rollback path. I sincerely hope Atlassian takes this seriously. Because many of us are already preparing to escalate this issue not just internally, but publicly. Best regards Falk

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

When will it be possible to switch back to the previous user interface or at least have real options

Falk Rüther

Subject: Severe UX Issues Following Layout Changes – Evaluation of Alternative Platforms Underway

Dear Atlassian Team,

We would like to inform you that the recent switch to the new Jira and Confluence layout, along with the current user experience (UX) interface, represents a serious disruption for our company. The new design is not only confusing for our team, but it also significantly impairs our daily workflow. The changes are so drastic and detrimental that they effectively amount to a provider switch – as our previously efficient way of working is no longer feasible.

We are therefore currently in contact with several alternative providers, including:

Microsoft 365 / Teams / Planner / SharePoint
Asana
Monday.com

According to community feedback and user experience reports, these platforms offer a noticeably better experience in many areas and receive significantly higher ratings on review platforms such as Trustpilot, G2, and Capterra compared to Atlassian.

We kindly ask for a statement on whether and when a return to a more user-friendly interface – or at the very least, a real choice for existing customers – can be expected. Otherwise, we will be forced to pursue a transition to one of the above-mentioned alternatives and document this step publicly on relevant review platforms.

Best regards

Accepted answers

Falk Rüther

Dear Marc,

Thank you for your reply – however, I must express that your response is, quite frankly, disrespectful to paying customers and unworthy of a professional discussion.

Your message completely ignores the scale and substance of the concerns raised. You dismiss a comprehensive, constructive critique with a casual “you are free to switch platforms”, while failing to acknowledge the real impact this forced UX transition is having across teams worldwide. Your tone implies that user frustration is optional – it is not.

Let me reiterate and clarify why this is not just a “matter of taste”:

There is no opt-out – Users are being forced into a new UX without choice, which contradicts standard enterprise-grade software practices.
Overloaded interface – Excessive icons, inconsistent spacing, and unclear design language now dominate the screen.
Key functions are harder to access – Basic workflows are now buried in unintuitive navigation paths.
Poor readability – Text elements clash with layout spacing, damaging clarity and reducing productivity.
Increased click depth – Simple actions now require far more effort and time than before.
Browser performance issues – Many users report severe lags, crashes, or inefficient rendering – particularly in long Confluence pages or complex Jira boards.
Browser inconsistency – UX behaves differently in Chrome, Firefox, and Safari – sometimes with broken or missing elements.
Navigation is confusing – Jira’s new layout makes it harder to switch between Epics, Backlogs, and Sprints without losing context.
Mobile usage is worse than ever – The new design is barely usable on tablets or phones.
No real benefit – The changes are cosmetic at best and degrade usability without offering any functional improvement.

Your comment did not address any of these points – and worse, it signals that Atlassian is not listening to its user base. Dismissing valid criticism as “free to switch platforms” is not only arrogant but strategically shortsighted. What you seem to miss is that this is not a minor adjustment. A significant share of experienced users is reaching a breaking point – and the shitstorm is already brewing. Just check the trending feedback on Trustpilot, Reddit, LinkedIn, or even within this very community forum.

We do not need flippant remarks. We need accountability and – at the very least – a roadmap toward an optional UX toggle, or an official rollback path.

I sincerely hope Atlassian takes this seriously. Because many of us are already preparing to escalate this issue not just internally, but publicly.

Best regards
Falk

All comments

Marc -Devoteam-

HI @Falk Rüther

Welcome to the community.

There is no option to return to the previous UI.

IF you are not happy with this change, you are free to switch to another platform.

NOTE: This is the Atlassian Community, not Atlassian Support.

https://support.atlassian.com/contact/

Of topic, Microsoft, Asana and Monday won't give you personal UI options as well.

Falk Rüther

Dear Marc,

Thank you for your reply – however, I must express that your response is, quite frankly, disrespectful to paying customers and unworthy of a professional discussion.

Let me reiterate and clarify why this is not just a “matter of taste”:

There is no opt-out – Users are being forced into a new UX without choice, which contradicts standard enterprise-grade software practices.
Overloaded interface – Excessive icons, inconsistent spacing, and unclear design language now dominate the screen.
Key functions are harder to access – Basic workflows are now buried in unintuitive navigation paths.
Poor readability – Text elements clash with layout spacing, damaging clarity and reducing productivity.
Increased click depth – Simple actions now require far more effort and time than before.
Browser performance issues – Many users report severe lags, crashes, or inefficient rendering – particularly in long Confluence pages or complex Jira boards.
Browser inconsistency – UX behaves differently in Chrome, Firefox, and Safari – sometimes with broken or missing elements.
Navigation is confusing – Jira’s new layout makes it harder to switch between Epics, Backlogs, and Sprints without losing context.
Mobile usage is worse than ever – The new design is barely usable on tablets or phones.
No real benefit – The changes are cosmetic at best and degrade usability without offering any functional improvement.

We do not need flippant remarks. We need accountability and – at the very least – a roadmap toward an optional UX toggle, or an official rollback path.

I sincerely hope Atlassian takes this seriously. Because many of us are already preparing to escalate this issue not just internally, but publicly.

Best regards
Falk

Falk Rüther

I’ve now responded to this thread three times, and each time my comment was deleted. Do I really need to take this discussion to Reddit or other public platforms for it to be acknowledged?

Falk Rüther

(EDIT: This comment was released from Spam Quarantine after previous comment from @Falk Rüther and after @Marc -Devoteam- 's reply shown below.)

Dear Marc,

Thank you for your reply – however, I must express that your response is, quite frankly, disrespectful to paying customers and unworthy of a professional discussion.

Let me reiterate and clarify why this is not just a “matter of taste”:

There is no opt-out – Users are being forced into a new UX without choice, which contradicts standard enterprise-grade software practices.
Overloaded interface – Excessive icons, inconsistent spacing, and unclear design language now dominate the screen.
Key functions are harder to access – Basic workflows are now buried in unintuitive navigation paths.
Poor readability – Text elements clash with layout spacing, damaging clarity and reducing productivity.
Increased click depth – Simple actions now require far more effort and time than before.
Browser performance issues – Many users report severe lags, crashes, or inefficient rendering – particularly in long Confluence pages or complex Jira boards.
Browser inconsistency – UX behaves differently in Chrome, Firefox, and Safari – sometimes with broken or missing elements.
Navigation is confusing – Jira’s new layout makes it harder to switch between Epics, Backlogs, and Sprints without losing context.
Mobile usage is worse than ever – The new design is barely usable on tablets or phones.
No real benefit – The changes are cosmetic at best and degrade usability without offering any functional improvement.

We do not need flippant remarks. We need accountability and – at the very least – a roadmap toward an optional UX toggle, or an official rollback path.

I sincerely hope Atlassian takes this seriously. Because many of us are already preparing to escalate this issue not just internally, but publicly.

Best regards

Falk

Marc -Devoteam-

@Falk Rüther

You can post anywhere if you want.

You are not required to use Atlassian. if you are not happy with the product, you are free to use another product.

Products are up for change and will be changed.

A vendor of a product will listen to users and might hear them, but they are not obliged.

Will you drop Netflix if there UI is not as you wish, do you think they will change it because YOU want it?

Trudy P Claspill

Hello @Falk Rüther

I found that some of your replies were automatically marked as Spam. I have released the non-duplicate ones so they should appear in this thread.

An alternate method to provide your feedback directly to Atlassian is to click the Help icon in Jira and select the Feedback option. That will send your feedback directly to Atlassian personnel.

Screenshot 2025-07-30 at 9.49.02 AM.png

Trudy P Claspill

There is also a post from Atlassian seeking end users (versus admins) to provide feedback on the new navigation. Perhaps you can apply to participate:

Seeking END-USERS to help us improve Atlassian’s navigation

Marc Koppelaar

That is still your opinion, isn’t it.

I’m just a user not from the company, and yes I also have doubts on the new UX.

Every change will impact a username and there will be always negatieve points.

Address them and they me be adjusted.

Contact your atlassian representative or Atlassian via support to take your concerns

But an opt-out as you mention is also on most platforms not an option, so what would you do in the future, if another of your critical business platform makes a change?

Regards

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud