No, I don't ! Therefore, I am unable to access to More actions (...) in the header of the project, only for software projects. It works well for business projects.
I created a software project named "Test nouvelle navigation" without creating an associated board. In this case, I am able :
to select the project from the sidebar,
to access to More actions (...) in the header of the project,
but I still don't get the feature Set project background.
And as soon as I create a board associated to this project, I loose all the possibilities I mentionned before, because I'm automatically brought back to the board.
hello can please someone help me know how to post a post in this forum? this is so freaking funny, i am not able to find a button to creata a new post; first time ever i see amazing user experience like this
We're currently shipping a lot of changes to Atlassian products that are in early stages (Early Access Program) which we will make available in our Figma files as the solutions become more stable and move to Beta and GA over the coming months. We'll let you know when these resources are available.
The new navigation is pretty refreshing, but the look of "blue" and "green" status are difficult to read compared to before the change.
In a large view like the screenshot it's barely ok, but in a smallest view the previous version was way more easy to read with the previous contrast (even if I'm surprised the actual constrast is ok in accessibility terms).
Am I the only one disturbed by this change ? Is it possible to do something ? I saw some people asking custom colors but maybe is it possible to give the choice between previous version and new one ?
Feedback of our users "The new design introduces a more minimalistic visual structure. While the top menu now blends more seamlessly with the board, it may take some time to adjust to the subtler separation. The updated work item icons have a lighter, more modern look, which might require a bit more focus to distinguish at first. For users with visual or concentration challenges, this change could present an initial hurdle. Personally, I find the interface now has a more uniform, neutral tone that may benefit from a bit more contrast to enhance clarity."
Bug: Pressing "hide" or "customise sidebar [uncheck projects]" has no effect. Project list still shows. [edit] after 24 hours, it now hides the Project list. Maybe Atl rolled out an urgent fix, maybe the code failed to manage browser-side cache properly. At least it works.
Bug: Using the ^ to minimise the project list is only effective until reloading the screen or opening another work item - when the list expands again, automatically.
Poor UI: (1) Using [>] to hide the sidebar entirely is only effective until needing to use the sidebar to navigate (e.g. to dashboard) (2) losing the top-menus means we can't avoid using the side-bar. We are also wasting time searching all over the screen for UI items, which is very awkward. (3) it also reveals if accidentally moused-over (should require a click).
PLEASE allow us to switch back to the old nav GLOBALLY by an admin!
I've been using the new navigation for several weeks now, and I like it less with each passing day.
It is annoying to have to continually expand/minimize the menus on the left to get to the projects, filters, dashboards, etc. that I use frequently, even if starred. It's decreased my efficiency.
To have to scroll down to the bottom of any topic (dashboard, filter, project, etc.) in order to "view all" is insane. The Projects is the only menu that gives the option with the three dots (...) to "manage projects", why isn't that available for EVERY topic?
Having it on the left pane wastes precious browser window space, requiring me to expand the window more than it used to or is functional. How do people handle this who don't have wide monitors, like when using a small laptop? I can't see how that is functional for anyone.
What problem(s) was these changes supposed to be solving? My vote is to reverse these changes. This was a horrendous mistake and Atlassian did not sample a broad enough cross section of its customers before deciding to push forward with this.
@Diane Logsdon You are 100,000% correct regarding using this new navigation layout on a laptop monitor... it's IMPOSSIBLE to use. This layout has reinforced my use of browser tab Groups with links to each JIRA view I use... i.e. 1 tab for my Scrum board, 1 tab for the Filter of the related issues, 1 tab for the Reports, 1 tab for the JIRA Plan Timeline view, etc.
One other "oddity" is that when there is room on the menu bar for the Shortcuts to be displayed, there is no way to show those other than selecting the dropdown, i.e. multiple clicks. I removed options such as Timeline, Goals, Forms, Code, etc. to have more room to see if I could display the actual shortcut link instead of having to 1st click on "Shortcuts"... :-(
@David Tieman , Thanks for your insight. I was wondering if using browser bookmarks, windows, tabs, and tab groups would alleviate some of the pain with Jira's new nav. Seems like orgs with lots of projects are the ones hurting.
I have not experienced the new nav yet. I expect it's coming to my org next month.
While we’ve seen strong quantitative success (like low opt-out rates and solid usage), we want to dig deeper intohowthe experience feels and functions in your day-to-day workflows. We’re opening up a research study for users and admins who have used the new navigation for at least two weeks.
@Don Arsenault I have been using the Browser Groups and Tabs for a long time as I have 10+ JIRA projects that I am actively engaged in. That doesn't include another Browser Group for Automation tab links for each of those projects. I was hopefully for some other benefits from the new navigation to reduce this need and setup. I guess that the one option that I would like to have would be to "hover and click" vs. "click and click".
Really struggling to understand the benefit of forcing users to navigate to a project's board(s) first instead of going straight to the list of issues. We have a number of teams that work straight within the projects themselves and don't utilize a Kanban board for their way of working. The default when navigating to a project from the "Recent" list in the left-hand navigation should be the normal default project view with the option to select the drop-down arrow to go to a board if present. The fact that currently you can click directly on a project without a board yet created, but are forced to select a board for other projects that already have one is very unintuitive in my opinion.
So I'm using this same comment on any page that talks about this horrible new Navigation.
I have to say it this new navigation is terrible. I honestly don’t understand why Atlassian would think it’s an improvement. It’s baffling, and it really sucks that you’re forcing everyone to use it. There are so many other areas that could use improvement, but instead, you decided to change the navigation which was already working just fine. This feels like a classic case of ignoring the saying, “If it ain’t broke, don’t fix it.” Now, the new navigation is confusing, and I can’t see any reason why you’d make this switch. It’s just bad.
Atlassian built its brand on engineers serving engineers. Abrupt UI overhauls—and removal of critical functions—are very misaligned with that heritage. We/I will also evaluate alternatives for all future efforts.
I’ve championed Jira and Confluence since 2004; they remain powerful products. But disruptive changes without adequate communication jeopardize user trust. I hope Atlassian re-engages with its core audience before more teams are forced to look elsewhere.
Will an option be available for a Project wide setting option that can be configured for all users of the project? Users would still be able to make changes for their view but based on the project wide setting. Basically I want to have all of the Shortcuts listed on the view for all users, I don't need Forms, Security, Archived Work Items, etc. And I don't want all of the project users have to make the same changes.
71 comments