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

Device list filtered by rack should include child devices #10266

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

Originally created by @dpotter-intoto on GitHub (Sep 19, 2024).

Originally assigned to: @arthanson on GitHub.

Deployment Type

Self-hosted

NetBox Version

v3.7.1

Python Version

3.10

Steps to Reproduce

  1. Create a child device
  2. Install it in a parent device's device-bay
  3. Navigate to devices
  4. Filter by the rack that the parent device is in
  5. Observe that the parent device is present in the list, but not the child device

Expected Behavior

I expected the child device to appear in the device list when the filter included the rack of the parent device.

Observed Behavior

The child device did not appear in the device list when the filter included the rack of the parent device.

Originally created by @dpotter-intoto on GitHub (Sep 19, 2024). Originally assigned to: @arthanson on GitHub. ### Deployment Type Self-hosted ### NetBox Version v3.7.1 ### Python Version 3.10 ### Steps to Reproduce 1. Create a child device 2. Install it in a parent device's device-bay 3. Navigate to devices 4. Filter by the rack that the parent device is in 5. Observe that the parent device is present in the list, but not the child device ### Expected Behavior I expected the child device to appear in the device list when the filter included the rack of the parent device. ### Observed Behavior The child device did not appear in the device list when the filter included the rack of the parent device.
adam added the type: bugpending closurestatus: revisions needed labels 2025-12-29 21:29:07 +01:00
adam closed this issue 2025-12-29 21:29:08 +01:00
adam commented 2025-12-29 21:29:08 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Sep 26, 2024):

@dpotter-intoto can you please re-check the reproduction steps as I'm not seeing this. You actually have to assign the child device to the site and rack of the parent device for it to show up in the assignment interface. When I go to the filter of the rack. In the screenshot below I have Device1 with a device bay and children device installed to it and when I filter I see both.

Also see the second screen-cap of the populate device bay where it shows the child device must be already assigned.
Devices | NetBox 2024-09-26 09-05-03
Populate tdevbay | NetBox 2024-09-26 09-06-15

@arthanson commented on GitHub (Sep 26, 2024): @dpotter-intoto can you please re-check the reproduction steps as I'm not seeing this. You actually have to assign the child device to the site and rack of the parent device for it to show up in the assignment interface. When I go to the filter of the rack. In the screenshot below I have Device1 with a device bay and children device installed to it and when I filter I see both. Also see the second screen-cap of the populate device bay where it shows the child device must be already assigned. ![Devices | NetBox 2024-09-26 09-05-03](https://github.com/user-attachments/assets/e21f9610-3fb6-465b-84e5-2c3cbfcf373c) ![Populate tdevbay | NetBox 2024-09-26 09-06-15](https://github.com/user-attachments/assets/016bd939-41e2-405a-9e69-ab76bed20461)
adam commented 2025-12-29 21:29:09 +01:00
Author
Owner
Copy Link

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

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (Oct 4, 2024): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
adam commented 2025-12-29 21:29:09 +01:00
Author
Owner
Copy Link

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

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@github-actions[bot] commented on GitHub (Oct 11, 2024): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
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 pending closure status: revisions needed type: bug
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#10266
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?