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

Locations not appearing under the correct parent #6233

New Issue
Closed
opened 2025-12-29 19:38:20 +01:00 by adam · 6 comments
adam commented 2025-12-29 19:38:20 +01:00
Owner
Copy Link

Originally created by @gigglestick on GitHub (Mar 19, 2022).

NetBox version

v3.1.9

Python version

3.9

Steps to Reproduce

  1. Manually create several locations.
  2. Create several child locations via CSV import with the parent set to locations in step 1.

Expected Behavior

Locations should appear under the correct parent and be sorted alphabetically within each level.

Observed Behavior

I have parents: Area A, Area B, Area C (Currently appearing in order Area A, Area C, Area B)
I have lots of children: Row A1-A, Row A1-B, Row A1-C, etc.

  • All Row A1-* entries are set to parent Area A, but some are appearing under Area C in the location list. If I click Area C, it shows no children.
  • If I assign some to Area C as the parent, they appear under Area B in the location list. If I click Area B, it shows no children.

20220318_1744_loc_edit
20220318_1744_loc_list

Originally created by @gigglestick on GitHub (Mar 19, 2022). ### NetBox version v3.1.9 ### Python version 3.9 ### Steps to Reproduce 1. Manually create several locations. 2. Create several child locations via CSV import with the parent set to locations in step 1. ### Expected Behavior Locations should appear under the correct parent and be sorted alphabetically within each level. ### Observed Behavior I have parents: Area A, Area B, Area C _(Currently appearing in order Area A, Area C, Area B)_ I have lots of children: Row A1-A, Row A1-B, Row A1-C, etc. - All Row A1-* entries are set to parent Area A, but some are appearing under Area C in the location list. If I click Area C, it shows no children. - If I assign some to Area C as the parent, they appear under Area B in the location list. If I click Area B, it shows no children. ![20220318_1744_loc_edit](https://user-images.githubusercontent.com/3887144/159098580-adbb1ec4-86aa-4361-8832-9f7d02063227.png) ![20220318_1744_loc_list](https://user-images.githubusercontent.com/3887144/159098595-963610b7-2133-4c39-b5c4-dbd635c17a33.png)
adam added the type: bugstatus: revisions needed labels 2025-12-29 19:38:20 +01:00
adam closed this issue 2025-12-29 19:38:20 +01:00
adam commented 2025-12-29 19:38:20 +01:00
Author
Owner
Copy Link

@gigglestick commented on GitHub (Mar 19, 2022):

I've tried clearing the parent and saving, so the children appear without a parent, then reassigning them to Area A again and they return to area C.

@gigglestick commented on GitHub (Mar 19, 2022): I've tried clearing the parent and saving, so the children appear without a parent, then reassigning them to Area A again and they return to area C.
adam commented 2025-12-29 19:38:21 +01:00
Author
Owner
Copy Link

@gigglestick commented on GitHub (Mar 19, 2022):

If I assign Row A1-F to Area C, it appears under Area B instead.

@gigglestick commented on GitHub (Mar 19, 2022): If I assign Row A1-F to Area C, it appears under Area B instead.
adam commented 2025-12-29 19:38:21 +01:00
Author
Owner
Copy Link

@gigglestick commented on GitHub (Mar 19, 2022):

All of the Row A1-* locations were created via CSV import where the parent was set to "Area A".

@gigglestick commented on GitHub (Mar 19, 2022): All of the Row A1-* locations were created via CSV import where the parent was set to "Area A".
adam commented 2025-12-29 19:38:21 +01:00
Author
Owner
Copy Link

@gigglestick commented on GitHub (Mar 19, 2022):

If I filter the location view where parent is Area A, all the right Row A1-* items show up. When I clear the filter, some appear Area B and appear under Area C.

@gigglestick commented on GitHub (Mar 19, 2022): If I filter the location view where parent is Area A, all the right Row A1-* items show up. When I clear the filter, some appear Area B and appear under Area C.
adam commented 2025-12-29 19:38:22 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 21, 2022):

Please revise your initial post above to include explicit reproduction steps, and to note exactly what you're seeing and what you expected to see. You need to provide detail sufficient for someone else to replicate the reported behavior.

@jeremystretch commented on GitHub (Mar 21, 2022): Please revise your initial post above to include explicit reproduction steps, and to note _exactly_ what you're seeing and what you expected to see. You need to provide detail sufficient for someone else to replicate the reported behavior.
adam commented 2025-12-29 19:38:22 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 29, 2022):

Closing this out as sufficient reproduction steps have not been provided. See #8987 for a potential fix in the absence of a known cause.

@jeremystretch commented on GitHub (Mar 29, 2022): Closing this out as sufficient reproduction steps have not been provided. See #8987 for a potential fix in the absence of a known cause.
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 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#6233
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?