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

Display related object fields as columns #11225

New Issue
Closed
opened 2025-12-29 21:42:10 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:42:10 +01:00
Owner
Copy Link

Originally created by @llamafilm on GitHub (May 27, 2025).

Originally assigned to: @llamafilm on GitHub.

NetBox version

v4.3.1

Feature type

Change to existing functionality

Proposed functionality

When customizing a table view, allow more related object fields to be displayed as columns. Specifically, I'd like to show Device Location and Device Site on the Interfaces table.

Use case

Before using Netbox, our teams used spreadsheets to track devices and IP addresses. I'm trying to create a view as close as possible to that. For example, a typical sheet would include these columns: Location name, Location number (custom field), Device description, Device ID, MAC, IP, patch point, switch name, switch interface, VLAN ID, Interface description.

The Interfaces table already allows some related object fields (Device Status), so it seems like not a big leap to add a few more.
Ideally, I would like to have access to all related object fields, including custom fields. That's unwieldy for the UI but I think it could work if we can build table configs using JSON.

Database changes

No response

External dependencies

No response

Originally created by @llamafilm on GitHub (May 27, 2025). Originally assigned to: @llamafilm on GitHub. ### NetBox version v4.3.1 ### Feature type Change to existing functionality ### Proposed functionality When customizing a table view, allow more related object fields to be displayed as columns. Specifically, I'd like to show Device Location and Device Site on the Interfaces table. ### Use case Before using Netbox, our teams used spreadsheets to track devices and IP addresses. I'm trying to create a view as close as possible to that. For example, a typical sheet would include these columns: Location name, Location number (custom field), Device description, Device ID, MAC, IP, patch point, switch name, switch interface, VLAN ID, Interface description. The Interfaces table already allows some related object fields (Device Status), so it seems like not a big leap to add a few more. Ideally, I would like to have access to _all_ related object fields, including custom fields. That's unwieldy for the UI but I think it could work if we can build table configs using JSON. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:42:10 +01:00
adam closed this issue 2025-12-29 21:42:10 +01:00
adam commented 2025-12-29 21:42:11 +01:00
Author
Owner
Copy Link

@llamafilm commented on GitHub (Aug 8, 2025):

Can you assign this to me please?

@llamafilm commented on GitHub (Aug 8, 2025): Can you assign this to me please?
adam commented 2025-12-29 21:42:11 +01:00
Author
Owner
Copy Link

@llamafilm commented on GitHub (Aug 29, 2025):

Can someone please clarify what is the process for adding new features? This issue has 2 thumbs up and a needs owner tag, and I volunteered to work on it. What's next? In CONTRIBUTING.md it says:

It's very important that you not submit a pull request until a relevant issue has been opened and assigned to you. Otherwise, you risk wasting time on work that may ultimately not be needed.

@llamafilm commented on GitHub (Aug 29, 2025): Can someone please clarify what is the process for adding new features? This issue has 2 thumbs up and a `needs owner` tag, and I volunteered to work on it. What's next? In [CONTRIBUTING.md](https://github.com/netbox-community/netbox/blob/main/CONTRIBUTING.md) it says: > It's very important that you not submit a pull request until a relevant issue has been opened and assigned to you. Otherwise, you risk wasting time on work that may ultimately not be needed.
adam commented 2025-12-29 21:42:12 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Sep 10, 2025):

Thanks, @llamafilm and apologies for missing your previous comments!

@jnovinger commented on GitHub (Sep 10, 2025): Thanks, @llamafilm and apologies for missing your previous comments!
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: low 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#11225
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?