Device color in rack elevations based on status #483

New Issue

MrUnknownDE · 2026-04-05T16:35:12+02:00

MrUnknownDE commented

2026-04-05 16:35:12 +02:00

Originally created by @jetseverschuren-novoserve on 1/23/2026

NetBox version

v4.5.1

Feature type

Change to existing functionality

Proposed functionality

Add a user preference to switch the device's colors in the racks elevation view to be based on status instead of device role.

The below line sets the device color. Modify that to check a user' config, and then either grab the color from device.role.color (current behavior) or device.status (requires a color lookup in DeviceStatusChoices.colors and ColorChoices).

4b4c542dce/netbox/dcim/svg/racks.py (L241)

I have a functioning PoC locally, so I could open a PR myself if there's enough interest to upstream this 🙂

My PoC currently also allows HEX value colors with custom states. The HEX colors break in the list view because that's based on classes, but we'd be okay with having to inject some custom CSS for that, even if otherwise it's otherwise not supported.

Use case

Our workflow is based relatively heavily around device states, so it would be more applicable for our DCops to quickly see device states based on the colors.

Database changes

It would add a user preference

External dependencies

None

*Originally created by @jetseverschuren-novoserve on 1/23/2026* ### NetBox version v4.5.1 ### Feature type Change to existing functionality ### Proposed functionality Add a user preference to switch the device's colors in the racks elevation view to be based on status instead of device role. The below line sets the device color. Modify that to check a user' config, and then either grab the color from `device.role.color` (current behavior) or `device.status` (requires a color lookup in `DeviceStatusChoices.colors` and `ColorChoices`). https://github.com/netbox-community/netbox/blob/4b4c542dced4dba6bd61241e3679cd3fed777ed4/netbox/dcim/svg/racks.py#L241 I have a functioning PoC locally, so I could open a PR myself if there's enough interest to upstream this 🙂 My PoC currently also allows HEX value colors with custom states. The HEX colors break in the list view because that's based on classes, but we'd be okay with having to inject some custom CSS for that, even if otherwise it's otherwise not supported. ### Use case Our workflow is based relatively heavily around device states, so it would be more applicable for our DCops to quickly see device states based on the colors. ### Database changes It would add a user preference ### External dependencies None

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 complexity: medium complexity: medium complexity: medium complexity: medium complexity: medium complexity: medium complexity: medium complexity: medium complexity: medium complexity: medium complexity: medium complexity: medium complexity: medium complexity: medium complexity: medium complexity: medium complexity: medium complexity: medium netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog 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#483