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

Don't hide locations parent when searching #7178

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

Originally created by @JoeIzzard on GitHub (Oct 28, 2022).

NetBox version

3.2.1

Feature type

Change to existing functionality

Proposed functionality

When searching the location field for example when adding a new rack, the parent locations should still be shown as multiple child locations can exist with different parents and the same name. For example, we have three venues with the same child locations, such as control room. When I add a rack to this location I have to go through the list as searching control room results in three results with no way to tell which is which.

Use case

For sites with multiple locations that have the same name. For example we have:

  • Venue 1-3
  • -> Control Room
  • -> Dimmer Room
  • -> Grid
  • -> Sound Control Room
  • -> DSM Control Room

When I search Control Room I currently get:

- Control Room
- Control Room
- Control Room

It would be ideal if instead we could have:

- Venue 1
-  -> Control Room
- Venue 2
-  -> Control Room
- Venue 3
-  -> Control Room

Database changes

None

External dependencies

None

Originally created by @JoeIzzard on GitHub (Oct 28, 2022). ### NetBox version 3.2.1 ### Feature type Change to existing functionality ### Proposed functionality When searching the location field for example when adding a new rack, the parent locations should still be shown as multiple child locations can exist with different parents and the same name. For example, we have three venues with the same child locations, such as control room. When I add a rack to this location I have to go through the list as searching control room results in three results with no way to tell which is which. ### Use case For sites with multiple locations that have the same name. For example we have: - Venue 1-3 - -> Control Room - -> Dimmer Room - -> Grid - -> Sound Control Room - -> DSM Control Room When I search Control Room I currently get: ``` - Control Room - Control Room - Control Room ``` It would be ideal if instead we could have: ``` - Venue 1 - -> Control Room - Venue 2 - -> Control Room - Venue 3 - -> Control Room ``` ### Database changes None ### External dependencies None
adam added the type: featurepending closure labels 2025-12-29 20:20:12 +01:00
adam closed this issue 2025-12-29 20:20:12 +01:00
adam commented 2025-12-29 20:20:13 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 2, 2022):

When you search for items in a dropdown, the API is matching on individual objects only. The behavior you're describing I'm afraid isn't possible without completely overhauling the filter backend. However, you can easily navigate by parent object instead.

@jeremystretch commented on GitHub (Nov 2, 2022): When you search for items in a dropdown, the API is matching on individual objects only. The behavior you're describing I'm afraid isn't possible without completely overhauling the filter backend. However, you can easily navigate by parent object instead.
adam commented 2025-12-29 20:20:13 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 2, 2023):

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 (Jan 2, 2023): 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).
adam commented 2025-12-29 20:20:14 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 1, 2023):

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 (Feb 1, 2023): 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.
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 type: feature
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#7178
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?