starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Possibility to change device when module #7243

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

Originally created by @dsl81 on GitHub (Nov 17, 2022).

NetBox version

3.3.8

Feature type

Change to existing functionality

Proposed functionality

Return ability to change device when editing module

Use case

Module can be moved between compatible bays on different devices. For example router line card or power supply can be inserted in any chassis but we cannot move it in netbox now. We can only change bays in one device. When editing module field "device" is disabled. Same as here https://github.com/netbox-community/netbox/issues/10447 if we have to recreate modules we will loose history of valuable equipment.
module

Database changes

No response

External dependencies

No response

Originally created by @dsl81 on GitHub (Nov 17, 2022). ### NetBox version 3.3.8 ### Feature type Change to existing functionality ### Proposed functionality Return ability to change device when editing module ### Use case Module can be moved between compatible bays on different devices. For example router line card or power supply can be inserted in any chassis but we cannot move it in netbox now. We can only change bays in one device. When editing module field "device" is disabled. Same as here https://github.com/netbox-community/netbox/issues/10447 if we have to recreate modules we will loose history of valuable equipment. ![module](https://user-images.githubusercontent.com/3961842/202460988-88e8eed5-d0b1-46e2-8b2b-b4a2665c4ae0.png) ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closurestatus: revisions needed labels 2025-12-29 20:20:49 +01:00
adam closed this issue 2025-12-29 20:20:49 +01:00
adam commented 2025-12-29 20:20:50 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Dec 18, 2022):

Can you elaborate on what the intended functionality is here? Moving modules do not move the associated components, so when moving modules before the components would stay on the same device and reference a module on another device, which is obviously not valid. Are you expecting the module to be moved barebones and the original components having their module reference nulled? As there is no way to repopulate module components, it seems like a weird usecase unless you are using modules with no components.

@kkthxbye-code commented on GitHub (Dec 18, 2022): Can you elaborate on what the intended functionality is here? Moving modules do not move the associated components, so when moving modules before the components would stay on the same device and reference a module on another device, which is obviously not valid. Are you expecting the module to be moved barebones and the original components having their module reference nulled? As there is no way to repopulate module components, it seems like a weird usecase unless you are using modules with no components.
adam commented 2025-12-29 20:20:50 +01:00
Author
Owner
Copy Link

@dsl81 commented on GitHub (Dec 20, 2022):

Moving a module should not move associated components. I expect that component reference to module shoud be removed. The component should remain on "old" device. Maybe option to remove associated components would be useful.

@dsl81 commented on GitHub (Dec 20, 2022): Moving a module should not move associated components. I expect that component reference to module shoud be removed. The component should remain on "old" device. Maybe option to remove associated components would be useful.
adam commented 2025-12-29 20:20:50 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 21, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Mar 21, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:20:51 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 20, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Apr 20, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: revisions needed 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#7243
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?