Atlassian's New Navigation UI (Jira, JSM and Confluence): A Call for More Transition Time

[#1]

Atlassian's initiative to introduce a new navigation UI is a step forward in modernizing its cloud platform. As loyal customers, we recognize the importance of evolving interfaces to enhance usability and efficiency. However, while the vision behind this change is commendable, the execution raises concerns—especially regarding the abrupt transition and unresolved UI issues.

Concerns:

• UI Inconsistencies: The new navigation UI still lacks polish in critical areas like font clarity, status colors, sidebar accessibility, and overall responsiveness.

• Forcing Adoption Too Soon: Many organizations, including ours, have recently migrated to the cloud and are still in the process of adjusting to the current interface. Forcing an immediate shift to a new UI disrupts user experience and generates resistance.

• User Frustration: Adoption of new interfaces takes time. Users need familiarity before transitioning again, and many teams are already struggling with the latest cloud migration.

A Request to Atlassian:

Rather than pushing this change forcefully, Atlassian should consider extending the rollout timeline until the end of 2025. This would allow customers to smoothly transition, address concerns, and ensure the UI is truly optimized before widespread adoption.

Atlassian has always thrived on customer feedback. A more gradual approach would reinforce trust, ensuring users feel heard rather than compelled to adjust too quickly.

We encourage fellow community members to share their experiences and thoughts. Let’s work together to make Atlassian’s cloud ecosystem better for everyone.

[Mathew Lederman]

@Sami Shaik I cannot like your post enough times to emphasize how much I truly agree.

One other point that I've shared with our CSM is that it will cost my organization >$1M USD in lost productivity. Assuming 5 hours of lost productivity per user × # of licensed users × average salary. We have no budgeted for this cost and our business units do not have the time to sacrifice learning a new, poorly implemented "solution" for a tool they depend on every day.

[Dwight Holman]

I agree - the changes do not seem 'finished' enough to launch in the current time-scale.

[Mark B Wager]

Agree. Extending the rollout timeline is a great plan for the express purpose of addressing issues and concerns raised in the various community forums.

I think we all want what Atlassian wants -- that is, to roll out a great product, with the features we want/need, at the right time, as problem-free as possible, and with loads of positive energy. 🙂

A launch-delay for time to refine the product a bit more could help deliver this.

Thanks!

Mark

[Rick Westbrock]

To be fair no matter when Atlassian forces the New Nav some customers will have just migrated to cloud so that doesn't really seem to be a valid reason to push out the deadline. That being said there are quite a few annoyances (and gaps which make it take longer to do something than it did in the old nav) which make it feel like they didn't do enough research with customers so it would be nice if they pushed out the deadline until those have been addressed (for examples see this post).