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

Allow changing module bay and/or device to which a module is assigned #9300

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

Originally created by @francesco-noc on GitHub (Feb 27, 2024).

NetBox version

v3.7.3

Feature type

New functionality

Proposed functionality

The topic was introduced in #13779 and #15162.

Once a module is created, it is bound to a specific module bay of a specific device. So apart from editing the descriptive fields (serial, asset_tag, ecc) , it can only be destroyed (deleted). It would be useful allowing move an existing module to another module bay of the same device or to a module bay of a different device, while keeping the descriptive fields unchanged and updating its components.
If a (destination) module bay is already in use, an error is returned.
Here you can find a working implementation.

Use case

Some organizations have to manage thousands of devices with thousands of modules, so it often happens that a module is removed from one device and installed in another device, or sometimes in other module bay of same device. This is exactly what happens with inventory items.

Database changes

None

External dependencies

None

Originally created by @francesco-noc on GitHub (Feb 27, 2024). ### NetBox version v3.7.3 ### Feature type New functionality ### Proposed functionality The topic was introduced in #13779 and #15162. Once a module is created, it is bound to a specific module bay of a specific device. So apart from editing the descriptive fields (serial, asset_tag, ecc) , it can only be destroyed (deleted). It would be useful allowing move an existing module to another module bay of the same device or to a module bay of a different device, while keeping the descriptive fields unchanged and updating its components. If a (destination) module bay is already in use, an error is returned. [Here](https://github.com/netbox-community/netbox/compare/develop...francesco-noc:netbox:13779-change-device-to-module) you can find a working implementation. ### Use case Some organizations have to manage thousands of devices with thousands of modules, so it often happens that a module is removed from one device and installed in another device, or sometimes in other module bay of same device. This is exactly what happens with inventory items. ### Database changes None ### External dependencies None
adam added the type: featurecomplexity: mediumnetboxstatus: backlog labels 2025-12-29 20:48:05 +01:00
adam commented 2025-12-29 20:48:05 +01:00
Author
Owner
Copy Link

@francesco-noc commented on GitHub (Jul 16, 2024):

Hi @jeremystretch, I see that no one is assigned to this task yet. If you want, I can port changes I made on version 3 to version 4.

@francesco-noc commented on GitHub (Jul 16, 2024): Hi @jeremystretch, I see that no one is assigned to this task yet. If you want, I can port changes I made on version 3 to version 4.
adam commented 2025-12-29 20:48:05 +01:00
Author
Owner
Copy Link

@francesco-noc commented on GitHub (Oct 8, 2024):

Hi, these changes also work with version 4.1.3 but I've not tested them with nested modules.

@francesco-noc commented on GitHub (Oct 8, 2024): Hi, [these changes](https://github.com/netbox-community/netbox/compare/develop...francesco-noc:netbox:13779-change-device-to-module) also work with version 4.1.3 but I've not tested them with nested modules.
adam commented 2025-12-29 20:48:06 +01:00
Author
Owner
Copy Link

@francesco-noc commented on GitHub (Dec 23, 2024):

Hi, is there any chance of having this functionality in future versions?

@francesco-noc commented on GitHub (Dec 23, 2024): Hi, is there any chance of having this functionality in future versions?
adam commented 2025-12-29 20:48:06 +01:00
Author
Owner
Copy Link

@francesco-noc commented on GitHub (May 13, 2025):

The same changes also work on 4.3.0

@francesco-noc commented on GitHub (May 13, 2025): The same changes also work on 4.3.0
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: medium netbox status: backlog 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#9300
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?