Add ability to display parent location on dcim locations table #8820

Closed
opened 2025-12-29 20:41:40 +01:00 by adam · 8 comments
Owner

Originally created by @drossy on GitHub (Nov 7, 2023).

NetBox version

v3.6.4

Feature type

Change to existing functionality

Proposed functionality

Add parent location to the fields able to be displayed on the Locations table displayed on /dcim/locations.

Use case

Adding the ability to display the parent Location on the /dcim/locations page would make it easier to distinguish between identically named Locations which have different Location hierarchies in the same Site.

We are looking to implement a new hierarchy in our netbox instance where our data centre is a Site and the multiple data centre rooms inside are Locations; and individual rows in those rooms are Locations whose parent is the Location corresponding to the appropriate room. These rows are labelled e.g. "Row 1", etc in each room. However the /dcim/locations table does not make it easy to distinguish between Row 1 in Room 1 and Row 1 in Room 2, as it only shows the Site.

Database changes

None I believe - parent is an existing entry in the location api object

External dependencies

None

Originally created by @drossy on GitHub (Nov 7, 2023). ### NetBox version v3.6.4 ### Feature type Change to existing functionality ### Proposed functionality Add parent location to the fields able to be displayed on the Locations table displayed on /dcim/locations. ### Use case Adding the ability to display the parent Location on the /dcim/locations page would make it easier to distinguish between identically named Locations which have different Location hierarchies in the same Site. We are looking to implement a new hierarchy in our netbox instance where our data centre is a Site and the multiple data centre rooms inside are Locations; and individual rows in those rooms are Locations whose parent is the Location corresponding to the appropriate room. These rows are labelled e.g. "Row 1", etc in each room. However the /dcim/locations table does not make it easy to distinguish between Row 1 in Room 1 and Row 1 in Room 2, as it only shows the Site. ### Database changes None I believe - parent is an existing entry in the location api object ### External dependencies None
adam added the type: featurestatus: needs ownerpending closurecomplexity: low labels 2025-12-29 20:41:40 +01:00
adam closed this issue 2025-12-29 20:41:40 +01:00
Author
Owner

@abhi1693 commented on GitHub (Nov 9, 2023):

I dont think this is a valid/actionable FR as the parent field on the locations page will be redundant due to the hierarchical structure which already exists.

image

@abhi1693 commented on GitHub (Nov 9, 2023): I dont think this is a valid/actionable FR as the parent field on the locations page will be redundant due to the hierarchical structure which already exists. ![image](https://github.com/netbox-community/netbox/assets/5083532/dd5b3dcc-110c-4504-a492-a9a86d79d260)
Author
Owner

@drossy commented on GitHub (Nov 10, 2023):

If you filter for the specific name of the child location then its becomes less obvious:
Screenshot 2023-11-10 at 09 53 46

@drossy commented on GitHub (Nov 10, 2023): If you filter for the specific name of the child location then its becomes less obvious: ![Screenshot 2023-11-10 at 09 53 46](https://github.com/netbox-community/netbox/assets/923739/cdbf1bc7-3c60-40af-96c5-4751bb62c7c2)
Author
Owner

@jeremystretch commented on GitHub (Dec 14, 2023):

We should also omit the leading hierarchy bullets from the "Name" column when a filter is in place.

@jeremystretch commented on GitHub (Dec 14, 2023): We should also omit the leading hierarchy bullets from the "Name" column when a filter is in place.
Author
Owner

@drossy commented on GitHub (Feb 9, 2024):

I'm happy to take a look at implementing this if no one else is going to?

@drossy commented on GitHub (Feb 9, 2024): I'm happy to take a look at implementing this if no one else is going to?
Author
Owner

@jeremystretch commented on GitHub (May 22, 2024):

@drossy are you still planning to work on this?

@jeremystretch commented on GitHub (May 22, 2024): @drossy are you still planning to work on this?
Author
Owner

@arthanson commented on GitHub (Jun 13, 2024):

un-assigning as no action on this.

@arthanson commented on GitHub (Jun 13, 2024): un-assigning as no action on this.
Author
Owner

@github-actions[bot] commented on GitHub (Sep 14, 2024):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Sep 14, 2024): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Oct 14, 2024):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Oct 14, 2024): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8820