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

Allow plugins to inject top-level navigation menu items #6318

New Issue
Closed
opened 2025-12-29 19:39:18 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:39:18 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Apr 7, 2022).

Originally assigned to: @arthanson, @jeremystretch on GitHub.

NetBox version

v3.2.0

Feature type

Change to existing functionality

Proposed functionality

Currently, plugins can define menu items only under the "Plugins" header within the navigation menu. Several plugin authors have proposed the ability for a plugin to "register" its own top-level section in the menu.

IMO the simplest approach would be to allow a plugin to define a menu heading with a title and icon. If defined, its menu items will appear there; if not, they will appear under the general "Plugins" heading.

We'd also want to give some thought to influencing the ordering of top-level menu items; assigning a "weight" to each item might suffice.

Use case

Greater visibility for plugin functions; control over order of placement (potentially?)

Database changes

No response

External dependencies

No response

Originally created by @jeremystretch on GitHub (Apr 7, 2022). Originally assigned to: @arthanson, @jeremystretch on GitHub. ### NetBox version v3.2.0 ### Feature type Change to existing functionality ### Proposed functionality Currently, plugins can define menu items only under the "Plugins" header within the navigation menu. Several plugin authors have proposed the ability for a plugin to "register" its own top-level section in the menu. IMO the simplest approach would be to allow a plugin to define a menu heading with a title and icon. If defined, its menu items will appear there; if not, they will appear under the general "Plugins" heading. We'd also want to give some thought to influencing the ordering of top-level menu items; assigning a "weight" to each item might suffice. ### Use case Greater visibility for plugin functions; control over order of placement (potentially?) ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: featuretopic: plugins labels 2025-12-29 19:39:18 +01:00
adam closed this issue 2025-12-29 19:39:18 +01:00
adam commented 2025-12-29 19:39:18 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 7, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jun 7, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:39:18 +01:00
Author
Owner
Copy Link

@peteeckel commented on GitHub (Jul 2, 2022):

I thought I'd revisit this now that a couple of months have passed and I implemented our plugin at two customers and in my own environment.

A complaint that I hear quite often is that access to plugins is somewhat hidden from view, which tends to confuse casual users. So I think the option of optionally "promoting" a plugin to be a first class menu entry is still on the wish list.

@peteeckel commented on GitHub (Jul 2, 2022): I thought I'd revisit this now that a couple of months have passed and I implemented our plugin at two customers and in my own environment. A complaint that I hear quite often is that access to plugins is somewhat hidden from view, which tends to confuse casual users. So I think the option of optionally "promoting" a plugin to be a first class menu entry is still on the wish list.
adam commented 2025-12-29 19:39:19 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Jul 2, 2022):

There should also be the ability to add our plugin menu under the existing headers like Virtualization or Devices etc. I have a few plugins that would be much suited under the existing ones rather than creating them as suggested in the description.

@abhi1693 commented on GitHub (Jul 2, 2022): There should also be the ability to add our plugin menu under the existing headers like `Virtualization` or `Devices` etc. I have a few plugins that would be much suited under the existing ones rather than creating them as suggested in the description.
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 status: accepted topic: plugins 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#6318
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?