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

Set default manufacturer on module insert #6508

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

Originally created by @shatt79 on GitHub (May 24, 2022).

Originally assigned to: @huntabyte on GitHub.

NetBox version

v3.2.3

Feature type

Change to existing functionality

Proposed functionality

When inserting a module into a device, the manufacturer of the module should default to the same manufacturer as the parent device. Eg, if I'm inserting a module into a Cisco ASR-9010, then the manufacturer of the module should be set to Cisco by default.

Use case

Saves time by not having to select the manufacturer of the module. The manufacturer of the module will almost always be the same as the manufacturer of the parent. The only exception being things like hard drive slots on servers and passive devices like modular distribution frames/patch panels. This is why the mfg field should only default to the parent's mfg and not be a read-only field.

Database changes

None

External dependencies

None

Originally created by @shatt79 on GitHub (May 24, 2022). Originally assigned to: @huntabyte on GitHub. ### NetBox version v3.2.3 ### Feature type Change to existing functionality ### Proposed functionality When inserting a module into a device, the manufacturer of the module should default to the same manufacturer as the parent device. Eg, if I'm inserting a module into a Cisco ASR-9010, then the manufacturer of the module should be set to Cisco by default. ### Use case Saves time by not having to select the manufacturer of the module. The manufacturer of the module will almost always be the same as the manufacturer of the parent. The only exception being things like hard drive slots on servers and passive devices like modular distribution frames/patch panels. This is why the mfg field should only **default** to the parent's mfg and not be a read-only field. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 19:41:45 +01:00
adam closed this issue 2025-12-29 19:41:45 +01:00
adam commented 2025-12-29 19:41:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 24, 2022):

This can be accomplished by pre-populating the device's manufacturer in the "add module" link: &manufacturer_id={{ object.device_type.manufacturer_id }} (something like that).

@jeremystretch commented on GitHub (May 24, 2022): This can be accomplished by pre-populating the device's manufacturer in the "add module" link: `&manufacturer_id={{ object.device_type.manufacturer_id }}` (something like that).
adam commented 2025-12-29 19:41:46 +01:00
Author
Owner
Copy Link

@shatt79 commented on GitHub (May 25, 2022):

Thanks! And where would one go to make those changes to the link?

On May 24, 2022, at 3:41 PM, Jeremy Stretch @.***> wrote:


This can be accomplished by pre-populating the device's manufacturer in the "add module" link: &manufacturer_id={{ object.device_type.manufacturer_id }} (something like that).

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

@shatt79 commented on GitHub (May 25, 2022): Thanks! And where would one go to make those changes to the link? > On May 24, 2022, at 3:41 PM, Jeremy Stretch ***@***.***> wrote: > >  > This can be accomplished by pre-populating the device's manufacturer in the "add module" link: &manufacturer_id={{ object.device_type.manufacturer_id }} (something like that). > > — > Reply to this email directly, view it on GitHub, or unsubscribe. > You are receiving this because you authored the thread.
adam commented 2025-12-29 19:41:47 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 25, 2022):

Sorry that was just a general note for anyone who would like to implement this. It's a change to be made in one (or more) of the HTML templates.

@jeremystretch commented on GitHub (May 25, 2022): Sorry that was just a general note for anyone who would like to implement this. It's a change to be made in one (or more) of the HTML templates.
adam commented 2025-12-29 19:41:47 +01:00
Author
Owner
Copy Link

@huntabyte commented on GitHub (Jun 19, 2022):

I can implement this functionality.

@huntabyte commented on GitHub (Jun 19, 2022): I can implement this functionality.
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: 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#6508
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?