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 #8510

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

Originally created by @shatt79 on GitHub (Aug 25, 2023).

Originally assigned to: @arthanson on GitHub.

NetBox version

v3.5.8

Feature type

Data model extension

Proposed functionality

This was implemented with #9563 in v3.2.5 but hasn't been working.

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

No response

External dependencies

No response

Originally created by @shatt79 on GitHub (Aug 25, 2023). Originally assigned to: @arthanson on GitHub. ### NetBox version v3.5.8 ### Feature type Data model extension ### Proposed functionality **This was implemented with #9563 in v3.2.5 but hasn't been working.** 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 _No response_ ### External dependencies _No response_
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 20:37:36 +01:00
adam closed this issue 2025-12-29 20:37:36 +01:00
adam commented 2025-12-29 20:37:37 +01:00
Author
Owner
Copy Link

@sleepinggenius2 commented on GitHub (Aug 25, 2023):

I can confirm that this still works as expected in 3.4, but it looks like it was not carried through when the new object selector was introduced in 3.5. Seems more like a bug to me.

@sleepinggenius2 commented on GitHub (Aug 25, 2023): I can confirm that this still works as expected in 3.4, but it looks like it was not carried through when the new object selector was introduced in 3.5. Seems more like a bug to me.
adam commented 2025-12-29 20:37:37 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 24, 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 (Nov 24, 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:37:37 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 19, 2023):

Reclassifying this as a bug per #9417

@jeremystretch commented on GitHub (Dec 19, 2023): Reclassifying this as a bug per #9417
adam commented 2025-12-29 20:37:37 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Apr 11, 2024):

This is no longer an issue in NB 4, Manufacturer is auto-set and not shown in edit. Closing

@arthanson commented on GitHub (Apr 11, 2024): This is no longer an issue in NB 4, Manufacturer is auto-set and not shown in edit. Closing
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 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#8510
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?