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 the "Related Objects" pane of all models dynamic #9508

New Issue
Closed
opened 2025-12-29 20:50:47 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:50:47 +01:00
Owner
Copy Link

Originally created by @alehaa on GitHub (Apr 20, 2024).

Originally assigned to: @alehaa on GitHub.

NetBox version

v3.7.5

Feature type

Change to existing functionality

Proposed functionality

In #13794, extending the "Related Objects" by other showing other models was requested and implemented by dynamically listing counts for all ManyToMany reverse relationships. Now, I'd like to copy this functionality to all other uses of the "Related Objects" pane,

Use case

As described in #13794, it might be useful for plugins to link their data to existing NetBox core models. However, this is not only useful for tenancy, but any object relationship could benefit from this.

A real life example is covered by the NetBox inventory plugin: Hardware assets are related to dcim.Device, dcim.Manufacturer, dcim.Site and dcim.Location. They would benefit from quick access to a list of related assets for these models. Right now an extra pane needs to be implemented, so there are actually two "Related Objects" panes per details page.

Also, this would make this feature work consistently across all views in NetBox, so the maintenance overhead should theoretically be reduced.

Database changes

None

External dependencies

None

Originally created by @alehaa on GitHub (Apr 20, 2024). Originally assigned to: @alehaa on GitHub. ### NetBox version v3.7.5 ### Feature type Change to existing functionality ### Proposed functionality In #13794, extending the "Related Objects" by other showing other models was requested and implemented by dynamically listing counts for all `ManyToMany` reverse relationships. Now, I'd like to copy this functionality to all other uses of the "Related Objects" pane, ### Use case As described in #13794, it might be useful for plugins to link their data to existing NetBox core models. However, this is not only useful for tenancy, but any object relationship could benefit from this. A real life example is covered by the [NetBox inventory](https://github.com/ArnesSI/netbox-inventory) plugin: Hardware assets are related to `dcim.Device`, `dcim.Manufacturer`, `dcim.Site` and `dcim.Location`. They would benefit from quick access to a list of related assets for these models. Right now an extra pane needs to be implemented, so there are actually two "Related Objects" panes per details page. Also, this would make this feature work consistently across all views in NetBox, so the maintenance overhead should theoretically be reduced. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: featurecomplexity: medium labels 2025-12-29 20:50:47 +01:00
adam closed this issue 2025-12-29 20:50:48 +01:00
adam commented 2025-12-29 20:50:49 +01:00
Author
Owner
Copy Link

@alehaa commented on GitHub (Apr 20, 2024):

I've already tested using the code from TenantView in other views and can provide a PR for the changes requested.

@alehaa commented on GitHub (Apr 20, 2024): I've already tested using the code from `TenantView` in other views and can provide a PR for the changes requested.
adam commented 2025-12-29 20:50:49 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Apr 22, 2024):

@alehaa sounds good, I'll assign to you - Note: you should capture the existing logic into a reusable function (vs. copying and pasting the current get_extra_context() for TenantView)

@arthanson commented on GitHub (Apr 22, 2024): @alehaa sounds good, I'll assign to you - Note: you should capture the existing logic into a reusable function (vs. copying and pasting the current get_extra_context() for TenantView)
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 complexity: medium status: accepted 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#9508
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?