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

Make plugin naviation easyer with utility functions #11906

New Issue
Closed
opened 2025-12-29 21:51:23 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:51:23 +01:00
Owner
Copy Link

Originally created by @Bapths on GitHub (Dec 8, 2025).

NetBox version

v4.4.7

Feature type

New functionality

Proposed functionality

Hi,

During the development of a NetBox plugin, I tough this would be useful to have similar utility functions such as get_model_buttons() and get_model_item() from netbox.navigation for plugin usage. This could be dedicated functions in netbox.plugins or a slight change to the existing functions so they support plugin views as well.

This mainly is the same as the existing functions with PluginMenuItem / PluginMenuButton classes instead ot MenuItem / MenuIntemButton and "plugins:" at the start of the link attribute.

Use case

This functionality could easily be added to the navigation.py file in the plugin, but since this is quite generic and becomes quite handy when dealing with lots of new models I think this could be an easy add-on to the original code for plugin developers.

Database changes

None

External dependencies

None

Originally created by @Bapths on GitHub (Dec 8, 2025). ### NetBox version v4.4.7 ### Feature type New functionality ### Proposed functionality Hi, During the development of a NetBox plugin, I tough this would be useful to have similar utility functions such as `get_model_buttons()` and `get_model_item()` from netbox.navigation for plugin usage. This could be dedicated functions in netbox.plugins or a slight change to the existing functions so they support plugin views as well. This mainly is the same as the existing functions with PluginMenuItem / PluginMenuButton classes instead ot MenuItem / MenuIntemButton and `"plugins:"` at the start of the `link` attribute. ### Use case This functionality could easily be added to the `navigation.py` file in the plugin, but since this is quite generic and becomes quite handy when dealing with lots of new models I think this could be an easy add-on to the original code for plugin developers. ### Database changes None ### External dependencies None
adam added the type: featurenetbox labels 2025-12-29 21:51:23 +01:00
adam closed this issue 2025-12-29 21:51:23 +01:00
adam commented 2025-12-29 21:51:24 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Dec 11, 2025):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@arthanson commented on GitHub (Dec 11, 2025): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/main/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
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 netbox 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#11906
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?