Admins Defining Starting Defaults for Left-Hand Sections along with Tabs

Greg D
Contributor
January 10, 2025

As an admin at every level, it would be extremely helpful to be able to set the default setup of navigation options for our users that are visible/hidden on the sidebar and that will unfurl within projects & other sections as a starting point. Loving the ability to make things more targeted and clean to have people focus on the most important work, but the nav can be cleaner and admins can assist.

  • The majority of our users are not well-versed enough to know the best setup as it applies to our Org, our particular sites, and specific Jira projects.
  • Atlassian's chosen defaults are not typically the best for our users and some things are currently not configurable at all (JSM sections).
  • Would be really helpful to have Atlassian's choice be the starting point for when admins make no choices, Org/Site admins can then alter that across the sites to have different starting defaults everywhere for all users, Project Admins can control what is nested in their project(s), and then all users can alter the main categories of navigation to their preference which will then persist for them (essentially giving users who do not choose anything the best navigation as Atlassian decides and then Org/Site/Project Admins can evolve it accordingly).
    • If a section name changes it would rename in place, but if a new section is introduced it can follow the same pattern
    • Seems that Project Admins in Software/Business projects can customize the horizontal tabs, but no one can set the best setup on the left-hand side for the other users and JSM projects in particular have a bunch of non-configurable sections that unfurl

 

 

As mentioned in that last point above, Jira Service Management projects and Jira Product Discovery projects still have a ton of sections in the sidebar when you unfurl them in the new navigation. JPD sections can be moved and deleted.  Will there be any way to customize what shows under a JSM project?  Like the thought behind tabs, there are a bunch of sections that may not be relevant to certain projects (e.g. JSM is showing many of the apps there that the developers may have setup incorrectly and it is confusing compared to the apps section and brings the users to the wrong place away from their project; some projects may not use queues and only use dashboards; some projects may not want user to raise a request through that sidebar link because they utilize a different help center; many projects do not utilize Reports nor the Knowledge Base sections, etc.).

Many Items that Cannot Be Removed Nor Reordered in JSM.png

2 comments

Comment

Log in or Sign up to comment
Lucas Modzelewski _Lumo_
Atlassian Partner
January 12, 2025

Great idea!

It can feel cluttered, and the most annoying part is probably the "Add shortcut" action.

When I was training interns, one of the steps was to create a bookmarks folder in browser and add links to the most important resources. This way, the most common pages are easily accessible and can be opened with a single click (at least in Chrome). As for the sidebar... it can stay closed. 😉

David Wilson
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 13, 2025

Hey Greg, I'm Dave a designer manager on the JSM team working on the new navigation, thanks for the great suggestion! Project level customisation is something we are actively exploring at the moment so this is a very timely post. Would you be interested in having a chat so I can learn more about your needs and for project level customisation? If you're keen, feel free to email me a dwilson@atlassian.com. Thanks again and look forward to chatting soon hopefully, Dave. 

TAGS
AUG Leaders

Atlassian Community Events