Add device description columns to DeviceComponentsTable #1198

New Issue

MrUnknownDE · 2026-04-05T21:52:18+02:00

MrUnknownDE commented

2026-04-05 21:52:18 +02:00

Originally created by @llamafilm on 9/24/2025

NetBox version

v4.4.0

Feature type

New functionality

Proposed functionality

I would also like to add an additional column for Device Description to all DeviceComponents tables.

And also add an Installed Device Description column to DeviceBay tables.

This does not add any database queries.

Use case

In our environment device descriptions are very important because most devices do not have a hostname. The name field is used only for devices which do have a meaningful hostname. For all the rest, we leave name blank to avoid uniqueness issues.

Here's an example to demonstrate the proposed functionality. We have two Adder ALIF4021T devices, which are mounted side by side in a single RU. To model this in Netbox, I have to model them as children, with a "generic 1U shelf" as the parent. The Device description field is how users tell the difference between the two devices on this shelf.
In this example, the Description column describes the bay itself, which is blank.
Device Description describes the shelf Device.
Installed Device Description describes the Device installed in the bay.

Database changes

none

External dependencies

none

*Originally created by @llamafilm on 9/24/2025* ### NetBox version v4.4.0 ### Feature type New functionality ### Proposed functionality I would also like to add an additional column for `Device Description` to all DeviceComponents tables. And also add an `Installed Device Description` column to DeviceBay tables. This does not add any database queries. ### Use case In our environment device descriptions are very important because most devices do not have a hostname. The `name` field is used only for devices which do have a meaningful hostname. For all the rest, we leave `name` blank to avoid uniqueness issues. Here's an example to demonstrate the proposed functionality. We have two Adder ALIF4021T devices, which are mounted side by side in a single RU. To model this in Netbox, I have to model them as children, with a "generic 1U shelf" as the parent. The Device `description` field is how users tell the difference between the two devices on this shelf. In this example, the `Description` column describes the bay itself, which is blank. `Device Description` describes the shelf Device. `Installed Device Description` describes the Device installed in the bay. <img width="1057" height="393" alt="Image" src="https://github.com/user-attachments/assets/40fc140f-51cd-429d-a49f-0e063496846f" /> ### Database changes none ### External dependencies none

MrUnknownDE closed this issue

2026-04-05 21:52:18 +02:00

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

No Label type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#1198