Closing participation for Beta

[#1]

Hi everyone,

Thank you for your participation in the EAP/Beta phase, which helped us gather feedback and shape the new navigation experience. We are now closing sign-ups for Beta to prepare for General Availability (GA) in March 2025.

What’s next?

We will begin transitioning everyone to the new navigation in March 2025. This experience will be available in Jira, Jira Service Management, Jira Product Discovery, Confluence, and Atlassian Home.

Have you already signed up?

If you’ve already signed up, then read how it affects you ⬇️

• If you signed up for the EAP/Beta with your site before 13 February 2025 (5 p.m. AEST), the new navigation will be enabled for your site.

• If your site is already on the new navigation, you and your users can continue using it. We won’t disable the new navigation for you.

Frequently asked questions

Question	Response/Answer
I signed up for EAP/Beta before February 13, 2025. Why haven’t I received the new navigation?	We’re dedicating 14 February 2025 to the final uploads. So, if admins signed up before 13 February 2025 and aren’t seeing new navigation on their sites by 14 February 2025, please send an email to mkroeger@atlassian.com.
I didn’t sign up for the new navigation. Why did my site still receive it?	For the new navigation to be enabled, an admin must sign up and provide the tenant ID or site URL. If your site has multiple admins, we recommend that you contact them to check if they’ve signed up for Beta. If your site is from the below cohort, we’ve enabled the new navigation without sign-ups for you: Sites on the Free edition Sandbox sites New users who’ve never used the old navigation in their sites before Additionally, your site will not have the option to opt out of the new navigation. While we’ve disabled opt-out, you can fill out this form or send an email to mkroeger@atlassian.com so we can disable the new navigation for your tenant ID or site URL.
Are there any resources I can read to understand more?	We’re committed to making this transition as easy as possible for all teams. While we work on making more resources available, here are some resources for you and your team: Learn more about the new navigation Join the New navigation Community group for more announcements See our recap of Atlassian’s Beta Launch and key product team insights Read our announcement on the Beta launch

Regards,
The Atlassian navigation team

[Roberto Ialino]

Hi, thanks for this post. Do you confirm that it will still be possible to disable it via Your Profile and Settings → Personal Settings → General → Jira Labs once it reaches GA? We need to inform our users.

Thanks a lot!

[Yatish Madhav]

Thanks @Varsha Patel  is there a way to know for sure when it will roll out to our instance? March 2025 seems to vague :) Can you give an exact date on GA or how can i see when this will be for our specific instance?

I want to communicate to our admins and 400+ users before hand.

Thank you

Yatish

[Trudy Claspill]

Where can we find the details for issues that were raised during the Beta/EAP that are not getting addressed before the roll out?

Here is information I culled from comments on Recap Atlassian's New Navigation Launch and key product team . This is just the "bugs" not suggestions for changes.

1. When I select "View all projects" and select a project, it opens in the main window, but the project doesn't appear in the "Recent" area until I do a refresh of my browser
2. The problem:the navigation panel does not refresh/repaint reliably. Sometimes when I navigate to Board Settings for an agile board the navigation panel does not refresh to show all the Board Settings options. I have to refresh the browser tab to get it to update.
3. Where does one find the option for viewing Archived Issues in the new navigation (available with the Premium subscription)? It is visible in the Project navigation (not under Project Settings)
   

[Jack Brickey]

Will there be a feedback channel for the Community post GA?

Full disclosure, I am not a big fan of the "explorer" sidebar. I find that I am constantly searching and stumbling, it certainly has slowed me down. I hope that changes in time. There are a number of things I need to access that are stuck at the bottom of the list in the sidebar. We have lost (or I haven't found) the reference to let us know if we are in a CMP or TMP.

[Harrison Ponce]

Thanks @Varsha Patel @Kristin Perchal !

The new navigation is cool and all, but the feature for displaying a custom product title is not working. This is pretty essential. For a lot of our users, the systems look very similar, especially for those that are not tech-savvy. Having the ability to display a product title is really useful.

Now in the new UI, without the titles, the products look almost identical. This is going to cause a lot of confusion and headache.

I think this is a bug or unintentional, as the settings where you would enable/modify the product title are still there in the settings for new navigation products, they just don't work to display the title...

See examples below:

I got support to open a bug for this:

• JRACLOUD-93385: Jira Title not showing in new UI

Curious if others are experiencing the same bug. Please vote and watch!

[Yatish Madhav]

@Varsha Patel  or Atlassian team, any specific date on when this will be rolled out to our instance? Want to make sure our teams are prepared for this change.

Thank you, Yatish

[Yatish Madhav]

Just to add to my previous comment from yesterday - i see this in our Product updates page ... but nothing relating to this? Please advise? Thank you

[Haddon Fisher]

I very much appreciate the effort Atlassian has taken thus far in informing the community about this change. The chrome extensions, many beta offers, and direct conversations all show a strong willingness from Atlassian to create spaces for feedback. 

The reaction (at least from what I can see) has been to deliver that feedback. These posts alone show a tremendous amount of specific & actionable information provided.

The one thing I do NOT see is that feedback being meaningfully engaged with and addressed.

I'm open to being wrong here; maybe I've missed seeing the changes in subsequent releases. However the stream of posts identifying concrete negative impacts on basic usability do not seem to be slowing down; instead, I see Atlassian posting responses with decreasing detail and frequency.

To be clear: I do not like these changes. I don't feel they solved any actual problems or delivered any net-new value, and it seems wildly irresponsible to disrupt long-standing, expected and well-known UX patterns for literally every single user unless it's absolutely necessary. However, I fully acknowledge that there's a bunch of people who have said they like this change and their feelings are as valid as mine.

My concern now is:

• Atlassian has a history of releasing major changes which result in significant UX pain for users and admins
• This change is unavoidable and will impact every single user
• There is a significant amount of feedback which does not seem to be even acknowledged, let alone addressed

It's incredibly frustrating to see this happen in the past, be asked this time "hey, we want to do better - tell us what you think" and then be ignored.