Display full rack group hierarchy when viewing a rack/device #4103

New Issue

adam · 2025-12-29T18:33:08+01:00

adam commented

2025-12-29 18:33:08 +01:00

Originally created by @ypid on GitHub (Sep 15, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

Python version: 3.7.3
NetBox version: 2.9.3

Proposed Functionality

Display full rack group hierarchy in /dcim/racks, /dcim/racks/{id} and /dcim/devices/{id}.

Use Case

As https://netbox.readthedocs.io/en/stable/core-functionality/sites-and-racks/ notes, rack groups can be hierarchical to model for example buildings -> floors -> rooms -> rack rows. Example values:

Factory building 1 -> Level 1 -> R101 -> Row 1

Currently, /dcim/racks/ only shows "Row 1" under "Group". At least in /dcim/racks/{id}, there is enough space to show the full hierarchy. Under /dcim/racks/ it could be a configurable column.

Similar under /dcim/devices/{id} except that here the last rack group hierarchy level is already shown. For the example: Row 1 -> Rack 1. Here it would be more helpful to write the full hierarchy.

What makes this currently even more tricky to use without redundancy is that clicking on the hyperlinks does not show you the hierarchy either.

Regions can also be hierarchical but I would argue that regions have a different semantic with the common use of geographical regions, there is basically a 1:n mapping (example Germany is in Europe) whereas rack groups can be n:m (with multiple "Row 1" and multiple "Level 1"). I would not necessarily apply the same logic to regions even though it could (/dcim/sites/{id} has also space in the table usually).

Database Changes

No.

External Dependencies

No.

Originally created by @ypid on GitHub (Sep 15, 2020). Originally assigned to: @jeremystretch on GitHub.  ### Environment * Python version: 3.7.3 * NetBox version: 2.9.3  ### Proposed Functionality Display full rack group hierarchy in `/dcim/racks`, `/dcim/racks/{id}` and `/dcim/devices/{id}`.  ### Use Case As https://netbox.readthedocs.io/en/stable/core-functionality/sites-and-racks/ notes, rack groups can be hierarchical to model for example `buildings -> floors -> rooms -> rack rows`. Example values: Factory building 1 -> Level 1 -> R101 -> Row 1 Currently, `/dcim/racks/` only shows "Row 1" under "Group". At least in `/dcim/racks/{id}`, there is enough space to show the full hierarchy. Under `/dcim/racks/` it could be a configurable column. Similar under `/dcim/devices/{id}` except that here the last rack group hierarchy level is already shown. For the example: `Row 1 -> Rack 1`. Here it would be more helpful to write the full hierarchy. What makes this currently even more tricky to use without redundancy is that clicking on the hyperlinks does not show you the hierarchy either. Regions can also be hierarchical but I would argue that regions have a different semantic with the common use of geographical regions, there is basically a 1:n mapping (example Germany is in Europe) whereas rack groups can be n:m (with multiple "Row 1" and multiple "Level 1"). I would not necessarily apply the same logic to regions even though it could (`/dcim/sites/{id}` has also space in the table usually).  ### Database Changes No.  ### External Dependencies No.

adam added the status: accepted type: feature labels 2025-12-29 18:33:08 +01:00

adam closed this issue

2025-12-29 18:33:08 +01:00

adam commented

2025-12-29 18:33:09 +01:00

@jeremystretch commented on GitHub (Sep 16, 2020):

We can extend the breadcrumbs (the lineage displayed at the top of the page) to include all parent rack groups, but the tables will need to stay as they are. You can view the assigned rack group to see it's full hierarchy, or navigate by the rack groups list.

@jeremystretch commented on GitHub (Sep 16, 2020): We can extend the breadcrumbs (the lineage displayed at the top of the page) to include all parent rack groups, but the tables will need to stay as they are. You can view the assigned rack group to see it's full hierarchy, or navigate by the rack groups list.

adam commented

2025-12-29 18:33:09 +01:00

@candlerb commented on GitHub (Sep 24, 2020):

Question: when viewing a device, is the rack supposed to be included in the breadcrumbs now?

With Netbox 2.9.4, when I go to /dcim/devices/<NN>/ I see breadcrumbs as

Devices / <sitename> / <devicename>

There is no rack, even though this is a racked device (note: I'm using racks without rackgroups)

If this is expected, then I'd suggest changing the issue title from "...when viewing a rack/device" to "...when viewing a rack"

@candlerb commented on GitHub (Sep 24, 2020): Question: when viewing a device, is the rack supposed to be included in the breadcrumbs now? With Netbox 2.9.4, when I go to `/dcim/devices/<NN>/` I see breadcrumbs as ``` Devices / <sitename> / <devicename> ``` There is no rack, even though this is a racked device (note: I'm using racks without rackgroups) If this is expected, then I'd suggest changing the issue title from "...when viewing a rack/device" to "...when viewing a rack"

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

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

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#4103