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

Related Interfaces are grayed out on multi inferface edit #11598

New Issue
Open
opened 2025-12-29 21:47:22 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:47:22 +01:00
Owner
Copy Link

Originally created by @jetedv on GitHub (Sep 11, 2025).

Originally assigned to: @pheus on GitHub.

NetBox Edition

NetBox Community

NetBox Version

V4.4.0

Python Version

3.10

Steps to Reproduce

  1. Select multiple interface on a device
  2. Click on "Edit Selected"
  3. No possible to select one of the Related Interfaces (Parent, Bridge, LAG) because the fields are grayed out

Expected Behavior

Normally we see all interfaces in these boxes

Observed Behavior

boxes are just grayed out

Originally created by @jetedv on GitHub (Sep 11, 2025). Originally assigned to: @pheus on GitHub. ### NetBox Edition NetBox Community ### NetBox Version V4.4.0 ### Python Version 3.10 ### Steps to Reproduce 1. Select multiple interface on a device 2. Click on "Edit Selected" 3. No possible to select one of the Related Interfaces (Parent, Bridge, LAG) because the fields are grayed out ### Expected Behavior Normally we see all interfaces in these boxes ### Observed Behavior boxes are just grayed out
adam added the type: bugstatus: acceptednetboxseverity: low labels 2025-12-29 21:47:22 +01:00
adam commented 2025-12-29 21:47:23 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Sep 12, 2025):

I believe this is the result of changes implementing #19735 (PR #19774), which saw a lot of the bulk actions machinery being refactored. In the shuffle, I believe the "Bulk Edit" button (and very likely other bulk actions buttons as well) lost the ability to add a device=<id> GET parameter to its formaction URL parameter when used inside of a object child view.

@jnovinger commented on GitHub (Sep 12, 2025): I believe this is the result of changes implementing #19735 (PR #19774), which saw a lot of the bulk actions machinery being refactored. In the shuffle, I believe the "Bulk Edit" button (and very likely other bulk actions buttons as well) lost the ability to add a `device=<id>` GET parameter to its `formaction` URL parameter when used inside of a object child view.
adam commented 2025-12-29 21:47:24 +01:00
Author
Owner
Copy Link

@pheus commented on GitHub (Dec 18, 2025):

Hi! Thanks for the report and the earlier analysis. This does look consistent with the bulk actions refactor.

I’ve been experimenting with a possible fix, but I’m not 100% sure it’s the preferred approach. My idea is to handle the “child view” case (e.g. device → interfaces) by detecting the parent object in the template context and then adding the parent’s pk (e.g. device=<pk>) into the bulk edit URL params inside the BulkEdit ObjectAction class. This restores the missing scoping so the “related interfaces” fields (Parent/Bridge/LAG) are populated/enabled during multi-edit.

If that direction sounds reasonable to the maintainers, I’m happy to open a PR so we can discuss the approach. Thanks again!

@pheus commented on GitHub (Dec 18, 2025): Hi! Thanks for the report and the earlier analysis. This does look consistent with the bulk actions refactor. I’ve been experimenting with a possible fix, but I’m not 100% sure it’s the preferred approach. My idea is to handle the “child view” case (e.g. device → interfaces) by detecting the parent object in the template context and then adding the parent’s `pk` (e.g. `device=<pk>`) into the bulk edit URL params inside the `BulkEdit` `ObjectAction` class. This restores the missing scoping so the “related interfaces” fields (Parent/Bridge/LAG) are populated/enabled during multi-edit. If that direction sounds reasonable to the maintainers, I’m happy to open a PR so we can discuss the approach. Thanks again!
adam commented 2025-12-29 21:47:24 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 18, 2025):

Thanks @pheus!

@jeremystretch commented on GitHub (Dec 18, 2025): Thanks @pheus!
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 netbox severity: low 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#11598
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?