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

add the ability to assign circuit group from the edit circuit page #10111

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

Originally created by @ghost on GitHub (Aug 17, 2024).

NetBox version

4.1-beta1

Feature type

Data model extension

Proposed functionality

in the new beta, when editing a circuit, there is no drop down multi-select to allow you to assign circuit groups directly from the 'edit circuit' page.
So far, the only way I've seen to assign a circuit to a circuit group is either from the circuit group assignments page, or from the circuit group page.
Without this addition, there is also no way to determine what group(s) a circuit is in on the edit circuit page. You can only get that information when looking at the circuit from other views.

This would likely take the form of a new section in the edit circuit page for 'circuit group', which contains the same selections as the 'assign a circuit' page.

image

image

Use case

allow the ability to assign a circuit group directly from the 'edit' page of a circuit.
This would make things consistent with other group assignment object types like contacts, tenants, clusters, etc.

Database changes

none

External dependencies

none.

Originally created by @ghost on GitHub (Aug 17, 2024). ### NetBox version 4.1-beta1 ### Feature type Data model extension ### Proposed functionality in the new beta, when editing a circuit, there is no drop down multi-select to allow you to assign circuit groups directly from the 'edit circuit' page. So far, the only way I've seen to assign a circuit to a circuit group is either from the circuit group assignments page, or from the circuit group page. Without this addition, there is also no way to determine what group(s) a circuit is in on the edit circuit page. You can only get that information when looking at the circuit from other views. This would likely take the form of a new section in the edit circuit page for 'circuit group', which contains the same selections as the 'assign a circuit' page. ![image](https://github.com/user-attachments/assets/a7e0e6ad-5a44-4af4-91f3-bbc8ce37bf42) ![image](https://github.com/user-attachments/assets/edbfdbf2-43da-4fdc-a416-96f156398903) ### Use case allow the ability to assign a circuit group directly from the 'edit' page of a circuit. This would make things consistent with other group assignment object types like contacts, tenants, clusters, etc. ### Database changes none ### External dependencies none.
adam added the type: featurestatus: blockednetboxcomplexity: high labels 2025-12-29 21:27:01 +01:00
adam commented 2025-12-29 21:27:02 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 22, 2024):

This is because the assignment of a circuit to a group involves an intermediary model (CircuitGroupAssignment), which holds additional information, as opposed to a simple ForeignKey relation.

There is no pattern in NetBox currently for this sort of dual-edit functionality, and I'm not sure it's a path we want to head down. But if we do, it will likely be only after the implementation of #5858, which should introduce some new and necessary UI capabilities.

@jeremystretch commented on GitHub (Oct 22, 2024): This is because the assignment of a circuit to a group involves an intermediary model (CircuitGroupAssignment), which holds additional information, as opposed to a simple ForeignKey relation. There is no pattern in NetBox currently for this sort of dual-edit functionality, and I'm not sure it's a path we want to head down. But if we do, it will likely be only after the implementation of #5858, which should introduce some new and necessary UI capabilities.
adam commented 2025-12-29 21:27:02 +01:00
Author
Owner
Copy Link

@dmulyalin commented on GitHub (Apr 9, 2025):

This is needed, it is almost impractical at lrger scale how it is done now where every circuit need to be placed into a group one by one manually instead of circuits bulk edit operation.

@dmulyalin commented on GitHub (Apr 9, 2025): This is needed, it is almost impractical at lrger scale how it is done now where every circuit need to be placed into a group one by one manually instead of circuits bulk edit operation.
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 complexity: high netbox status: blocked 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#10111
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?