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

Remove/hide related devices #5782

New Issue
Closed
opened 2025-12-29 19:32:37 +01:00 by adam · 9 comments
adam commented 2025-12-29 19:32:37 +01:00
Owner
Copy Link

Originally created by @hagbarddenstore on GitHub (Dec 15, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.1.1

Feature type

Change to existing functionality

Proposed functionality

Remove or hide the related devices box on the device page.

Use case

The current method of finding related devices is quite confusing and not really usable because of which criterions it finds them by.

It is quite common to have several hundred devices of the same role within the same site, of which the related devices box shows only ten, in no particular order.

It would be an improvement if it found them within the same rack or by cable connections or something narrower than role+site.

Database changes

No response

External dependencies

No response

Originally created by @hagbarddenstore on GitHub (Dec 15, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.1.1 ### Feature type Change to existing functionality ### Proposed functionality Remove or hide the related devices box on the device page. ### Use case The current method of finding related devices is quite confusing and not really usable because of which criterions it finds them by. It is quite common to have several hundred devices of the same role within the same site, of which the related devices box shows only ten, in no particular order. It would be an improvement if it found them within the same rack or by cable connections or something narrower than role+site. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:32:38 +01:00
adam closed this issue 2025-12-29 19:32:38 +01:00
adam commented 2025-12-29 19:32:38 +01:00
Author
Owner
Copy Link

@sdktr commented on GitHub (Dec 15, 2021):

Would be cool if the query for the definition of 'related devices' could be stored in config. Limiting the amount of results to X-amount and providing a link to the full results.

related_devices_query: ?role={{ obj.role }}&site={{ obj.site }}
related_devices_maxresult = 5

This results in including: ?role={{ obj.role }}&site={{ obj.site }}&max_result=5

to be included on the device page. With a link to /devices?role={{ obj.role }}&site={{ obj.site }} in the view as well.

@sdktr commented on GitHub (Dec 15, 2021): Would be cool if the query for the definition of 'related devices' could be stored in config. Limiting the amount of results to X-amount and providing a link to the full results. related_devices_query: ?role={{ obj.role }}&site={{ obj.site }} related_devices_maxresult = 5 This results in including: ?role={{ obj.role }}&site={{ obj.site }}&max_result=5 to be included on the device page. With a link to /devices?role={{ obj.role }}&site={{ obj.site }} in the view as well.
adam commented 2025-12-29 19:32:38 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Dec 15, 2021):

Following on from the slack chat that started this issue.

In general it would be nice to have a small list of config options for hiding / disabling small ui features.

For example it would be nice if there was a config option to hide custom fields with no value set.
The defaults could be to have these panels / options enabled.

So an option for "hide_related_devices" and "hide_unset_custom_fields" for example

@ITJamie commented on GitHub (Dec 15, 2021): Following on from the slack chat that started this issue. In general it would be nice to have a small list of config options for hiding / disabling small ui features. For example it would be nice if there was a config option to hide custom fields with no value set. The defaults could be to have these panels / options enabled. So an option for "hide_related_devices" and "hide_unset_custom_fields" for example
adam commented 2025-12-29 19:32:39 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Dec 15, 2021):

Re: related devices query. Id like to see it be based off devices connected to it or devices in the same rack more than site level. Sites can be huge.

@ITJamie commented on GitHub (Dec 15, 2021): Re: related devices query. Id like to see it be based off devices connected to it or devices in the same rack more than site level. Sites can be huge.
adam commented 2025-12-29 19:32:39 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Dec 16, 2021):

@hagbarddenstore

I see two distinct FR's in your request, which one do you actually want to proceed with?

  1. Allow hiding of related devices
  2. Alter the related devices lookup to show more relevant devices
@DanSheps commented on GitHub (Dec 16, 2021): @hagbarddenstore I see two distinct FR's in your request, which one do you actually want to proceed with? 1. Allow hiding of related devices 2. Alter the related devices lookup to show more relevant devices
adam commented 2025-12-29 19:32:39 +01:00
Author
Owner
Copy Link

@hagbarddenstore commented on GitHub (Dec 16, 2021):

@DanSheps Well, no. The feature request is about user experience and discussion around which alternative is the best choice to improve the user experience.

Given the comments here and on Slack, it seems that we should do the second alternative, rather than removing it entirely.

@hagbarddenstore commented on GitHub (Dec 16, 2021): @DanSheps Well, no. The feature request is about user experience and discussion around which alternative is the best choice to improve the user experience. Given the comments here and on Slack, it seems that we should do the second alternative, rather than removing it entirely.
adam commented 2025-12-29 19:32:39 +01:00
Author
Owner
Copy Link

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

I'm in favor of removing it entirely. It was introduced long before the plugins API made it possible to embed custom content within the view, which would be the recommended approach for anyone who wishes to do so.

@jeremystretch commented on GitHub (Dec 16, 2021): I'm in favor of removing it entirely. It was introduced long before the plugins API made it possible to embed custom content within the view, which would be the recommended approach for anyone who wishes to do so.
adam commented 2025-12-29 19:32:40 +01:00
Author
Owner
Copy Link

@hagbarddenstore commented on GitHub (Dec 16, 2021):

I like this suggestion :D

@hagbarddenstore commented on GitHub (Dec 16, 2021): I like this suggestion :D
adam commented 2025-12-29 19:32:40 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Dec 17, 2021):

Yeah, sounds like a good idea IMO

@DanSheps commented on GitHub (Dec 17, 2021): Yeah, sounds like a good idea IMO
adam commented 2025-12-29 19:32:40 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Dec 17, 2021):

If it is going away. Id really reccomended moving one of the panel items on the left to the right in device view. Custom fields, tags comments. Theres a lot on the left section

@ITJamie commented on GitHub (Dec 17, 2021): If it is going away. Id really reccomended moving one of the panel items on the left to the right in device view. Custom fields, tags comments. Theres a lot on the left section
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 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#5782
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?