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

Matching interface descriptions are not shown in search results #2509

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

Originally created by @raddessi on GitHub (Apr 11, 2019).

Environment

  • Python version: Python 3.6.2 :: Continuum Analytics, Inc.
  • NetBox version: 2.5.8

Proposed Functionality

When searching for text that matches a port descripton, that connection (or device? interface?) should be shown in the search results.

Use Case

Searching for ports, else it seems to me like good info for a general search if it matches

Database Changes

None AFAIK

External Dependencies

None AFAIK

Originally created by @raddessi on GitHub (Apr 11, 2019). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: Python 3.6.2 :: Continuum Analytics, Inc. * NetBox version: 2.5.8 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality When searching for text that matches a port descripton, that connection (or device? interface?) should be shown in the search results. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case Searching for ports, else it seems to me like good info for a general search if it matches <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes None AFAIK <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies None AFAIK
adam closed this issue 2025-12-29 18:19:30 +01:00
adam commented 2025-12-29 18:19:30 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 11, 2019):

Please include steps that someone else can take to recreate the issue. Also upgrade to the current stable release (v2.5.10).

@jeremystretch commented on GitHub (Apr 11, 2019): Please include steps that someone else can take to recreate the issue. Also upgrade to the current stable release (v2.5.10).
adam commented 2025-12-29 18:19:30 +01:00
Author
Owner
Copy Link

@raddessi commented on GitHub (Apr 11, 2019):

Sure.

  1. Create a device with any interface
  2. Set the interface desc to my-iface-desc
  3. Search in the global search field for my-iface-desc

No results are shown for me

@raddessi commented on GitHub (Apr 11, 2019): Sure. 1. Create a device with any interface 1. Set the interface desc to `my-iface-desc` 1. Search in the global search field for `my-iface-desc` No results are shown for me
adam commented 2025-12-29 18:19:31 +01:00
Author
Owner
Copy Link

@raddessi commented on GitHub (Apr 11, 2019):

OK, we will upgrade as well. Will respond asap.

@raddessi commented on GitHub (Apr 11, 2019): OK, we will upgrade as well. Will respond asap.
adam commented 2025-12-29 18:19:31 +01:00
Author
Owner
Copy Link

@raddessi commented on GitHub (Apr 17, 2019):

We upgraded to 2.5.10 and the issue still persists

@raddessi commented on GitHub (Apr 17, 2019): We upgraded to 2.5.10 and the issue still persists
adam commented 2025-12-29 18:19:31 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 1, 2019):

The global search does not match on any device components for performance reasons. We could add them to the device search, but I suspect that would end up returning too much noise when people are looking for specific devices.

@jeremystretch commented on GitHub (May 1, 2019): The global search does not match on any device components for performance reasons. We could add them to the device search, but I suspect that would end up returning too much noise when people are looking for specific devices.
adam commented 2025-12-29 18:19:31 +01:00
Author
Owner
Copy Link

@raddessi commented on GitHub (May 4, 2019):

Ok, I get that. Unfortunately this would be very useful for us at least so it would be great if we could add some method to do this..

How about adding a checkbox to the filter list for something like Include results for device components then? This would have the side effect of making it more clear that these are not included by default.

@raddessi commented on GitHub (May 4, 2019): Ok, I get that. Unfortunately this would be very useful for us at least so it would be great if we could add some method to do this.. How about adding a checkbox to the filter list for something like `Include results for device components` then? This would have the side effect of making it more clear that these are not included by default.
adam commented 2025-12-29 18:19:31 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 24, 2019):

Matching on device component attributes in global search is not warranted/feasible. Closing this out.

@jeremystretch commented on GitHub (Jun 24, 2019): Matching on device component attributes in global search is not warranted/feasible. Closing this out.
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
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#2509
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?