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

Cables Type Filter prefiled with wrong Type #2397

New Issue
Closed
opened 2025-12-29 17:25:43 +01:00 by adam · 1 comment
adam commented 2025-12-29 17:25:43 +01:00
Owner
Copy Link

Originally created by @tb-killa on GitHub (Feb 19, 2019).

Environment

  • Python version: 3.6
  • NetBox version: 2.5.6

Steps to Reproduce

  1. Create two Device for e.g. Patchpanel
  2. Connect both Rear Ports with Cable and Select for Type e.g. CAT7
  3. Go to Devices -> Cables and read the created Connection in Table View compare to the Predefined Search Element in the Right Searchbar.

Expected Behavior

The Cable Type in the Search-Bar should be match to the Connections in the Table themselve.

Observed Behavior

It shows as default "CAT3" in the Type Field of the Search Box.

image

Originally created by @tb-killa on GitHub (Feb 19, 2019). ### Environment * Python version: 3.6 * NetBox version: 2.5.6 ### Steps to Reproduce 1. Create two Device for e.g. Patchpanel 2. Connect both Rear Ports with Cable and Select for Type e.g. CAT7 3. Go to Devices -> Cables and read the created Connection in Table View compare to the Predefined Search Element in the Right Searchbar. <!-- What did you expect to happen? --> ### Expected Behavior The Cable Type in the Search-Bar should be match to the Connections in the Table themselve. <!-- What happened instead? --> ### Observed Behavior It shows as default "CAT3" in the Type Field of the Search Box. ![image](https://user-images.githubusercontent.com/932481/52999053-1c047800-3425-11e9-9025-a4daa2f233bc.png)
adam added the type: bugstatus: accepted labels 2025-12-29 17:25:43 +01:00
adam closed this issue 2025-12-29 17:25:43 +01:00
adam commented 2025-12-29 17:25:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 20, 2019):

To clarify, this behavior is irrelevant to the types of cables defined: The form field should always be empty by default.

@jeremystretch commented on GitHub (Feb 20, 2019): To clarify, this behavior is irrelevant to the types of cables defined: The form field should always be empty by default.
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: accepted 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#2397
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?