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

No longer able to select a range of rear ports to associate with a group of front ports #8032

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

Originally created by @shatt79 on GitHub (May 10, 2023).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

3.5

Feature type

Change to existing functionality

Proposed functionality

Prior to 3.5, when creating front ports on a device, we could shift+click a range of rear ports to tie the front ports to. Now, we have to click rear ports one at a time. I'd like for the old method to return, if possible.

Use case

When creating 288ct patch panels, it's extremely cumbersome to have to individually click each rear port. What used to take 2 seconds now takes 20+ minutes. Being able to select a range of rear ports will greatly speed up this process.

Database changes

No response

External dependencies

No response

Originally created by @shatt79 on GitHub (May 10, 2023). Originally assigned to: @jeremystretch on GitHub. ### NetBox version 3.5 ### Feature type Change to existing functionality ### Proposed functionality Prior to 3.5, when creating front ports on a device, we could shift+click a range of rear ports to tie the front ports to. Now, we have to click rear ports one at a time. I'd like for the old method to return, if possible. ### Use case When creating 288ct patch panels, it's extremely cumbersome to have to individually click each rear port. What used to take 2 seconds now takes 20+ minutes. Being able to select a range of rear ports will greatly speed up this process. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: bugstatus: accepted labels 2025-12-29 20:31:31 +01:00
adam closed this issue 2025-12-29 20:31:31 +01:00
adam commented 2025-12-29 20:31:32 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (May 10, 2023):

I don't think this was intended, so not sure if this is actually a feature request. I think it changed as part of the stuff @jeremystretch did with regards to allowing components to be added from the sidebar link.

@kkthxbye-code commented on GitHub (May 10, 2023): I don't think this was intended, so not sure if this is actually a feature request. I think it changed as part of the stuff @jeremystretch did with regards to allowing components to be added from the sidebar link.
adam commented 2025-12-29 20:31:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 10, 2023):

Was just looking into this; can confirm it's a bug and was not intentional. I think it actually stems from some earlier changes I made to the BootstrapMixin class which are affecting how the widget is being rendered. We don't have many multi-select fields that render as expanded as fields, so I'm guessing this was simply overlooked. Need to dig into it some more.

@jeremystretch commented on GitHub (May 10, 2023): Was just looking into this; can confirm it's a bug and was not intentional. I think it actually stems from some earlier changes I made to the `BootstrapMixin` class which are affecting how the widget is being rendered. We don't have many multi-select fields that render as expanded as fields, so I'm guessing this was simply overlooked. Need to dig into it some more.
adam commented 2025-12-29 20:31:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 10, 2023):

Yep, I needed to tweak BootstrapMixin. It's back to normal now. Thanks for calling this out @shatt79!

@jeremystretch commented on GitHub (May 10, 2023): Yep, I needed to tweak `BootstrapMixin`. It's back to normal now. Thanks for calling this out @shatt79!
adam commented 2025-12-29 20:31:32 +01:00
Author
Owner
Copy Link

@shatt79 commented on GitHub (May 10, 2023):

Wow! Thanks for the quick response! Will this be in the next release? 3.5.2?

@shatt79 commented on GitHub (May 10, 2023): Wow! Thanks for the quick response! Will this be in the next release? 3.5.2?
adam commented 2025-12-29 20:31:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 10, 2023):

Yep, it will be in v3.5.2.

@jeremystretch commented on GitHub (May 10, 2023): Yep, it will be in v3.5.2.
adam commented 2025-12-29 20:31:33 +01:00
Author
Owner
Copy Link

@shatt79 commented on GitHub (May 24, 2023):

@jeremystretch
I'm still seeing the same behavior in 3.5.2. I can only click one rear port at a time when adding front ports. Is there some kind of keyboard shortcut I'm missing?

@shatt79 commented on GitHub (May 24, 2023): @jeremystretch I'm still seeing the same behavior in 3.5.2. I can only click one rear port at a time when adding front ports. Is there some kind of keyboard shortcut I'm missing?
adam commented 2025-12-29 20:31:33 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (May 24, 2023):

@shatt79

I'm still seeing the same behavior in 3.5.2. I can only click one rear port at a time when adding front ports. Is there some kind of keyboard shortcut I'm missing?

Looks fine for me:

https://demo.netbox.dev/dcim/front-ports/add/?device=125&return_url=/dcim/devices/125/front-ports/

image

@kkthxbye-code commented on GitHub (May 24, 2023): @shatt79 > I'm still seeing the same behavior in 3.5.2. I can only click one rear port at a time when adding front ports. Is there some kind of keyboard shortcut I'm missing? Looks fine for me: https://demo.netbox.dev/dcim/front-ports/add/?device=125&return_url=/dcim/devices/125/front-ports/ ![image](https://github.com/netbox-community/netbox/assets/400797/8882b36d-486d-4e14-b0a6-7b578efde0dd)
adam commented 2025-12-29 20:31:34 +01:00
Author
Owner
Copy Link

@shatt79 commented on GitHub (May 24, 2023):

Hmm...

image

@shatt79 commented on GitHub (May 24, 2023): Hmm... ![image](https://github.com/netbox-community/netbox/assets/103387334/4f74557c-96db-4289-9479-ed17555eb7ea)
adam commented 2025-12-29 20:31:34 +01:00
Author
Owner
Copy Link

@shatt79 commented on GitHub (May 24, 2023):

Ahh... so it works when creating front ports on an existing device, but not when creating the front port templates on a device-type.

@shatt79 commented on GitHub (May 24, 2023): Ahh... so it works when creating front ports on an existing device, but not when creating the front port templates on a device-type.
adam commented 2025-12-29 20:31:34 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (May 24, 2023):

@shatt79 gotcha, please create a new issue with the new replication steps.

@kkthxbye-code commented on GitHub (May 24, 2023): @shatt79 gotcha, please create a new issue with the new replication steps.
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#8032
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?