starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Custom menu order #5741

New Issue
Closed
opened 2025-12-29 19:32:05 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:32:05 +01:00
Owner
Copy Link

Originally created by @PieterL75 on GitHub (Dec 7, 2021).

NetBox version

v3.1.0

Feature type

Change to existing functionality

Proposed functionality

The current menu is in a fixed order.
Organization - Devices - Connections - Wireless - IPAM - Virtualization - Circuits - Power - Other - Plugins

This order is not optimal for each use case, or some features are not required.

Can it made possible to order the menu structure and optionally hide other ?

Use case

Not all features of Netbox are used by each implementation.
In our case, we are not documenting Wireless or Virtualization items.

My optimal menu structure would be
Devices - IPAM - Organization - Circuits - Power - Connections - Other - Plugins - Virtualization - Wireless

Database changes

not really. This could be accomplished in the configuration.py.
Optionally an extra field in the 'admin/groups' to set the order per group of people

External dependencies

No response

Originally created by @PieterL75 on GitHub (Dec 7, 2021). ### NetBox version v3.1.0 ### Feature type Change to existing functionality ### Proposed functionality The current menu is in a fixed order. Organization - Devices - Connections - Wireless - IPAM - Virtualization - Circuits - Power - Other - Plugins This order is not optimal for each use case, or some features are not required. Can it made possible to order the menu structure and optionally hide other ? ### Use case Not all features of Netbox are used by each implementation. In our case, we are not documenting Wireless or Virtualization items. My optimal menu structure would be Devices - IPAM - Organization - Circuits - Power - Connections - Other - Plugins - Virtualization - Wireless ### Database changes not really. This could be accomplished in the configuration.py. Optionally an extra field in the 'admin/groups' to set the order per group of people ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:32:05 +01:00
adam closed this issue 2025-12-29 19:32:05 +01:00
adam commented 2025-12-29 19:32:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 7, 2021):

Sorry, but this degree of customization is not a design goal for NetBox. It would impose significant development burden with relatively little value.

@jeremystretch commented on GitHub (Dec 7, 2021): Sorry, but this degree of customization is not a design goal for NetBox. It would impose significant development burden with relatively little value.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#5741
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?