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 multiple models for object selection custom field type #10867

New Issue
Closed
opened 2025-12-29 21:36:58 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:36:58 +01:00
Owner
Copy Link

Originally created by @Azmodeszer on GitHub (Mar 11, 2025).

NetBox version

v4.2.5

Feature type

Change to existing functionality

Proposed functionality

Currently, when selecting the custom field type Object or Multiple objects, it's only possible to choose a single model under Related object type. Are there any hurdles with simply allowing multiple?

Use case

My personal use case is a custom field for linking to a test or production instance of a VM or device. I currently have the related object model set to Virtual Machine since that covers most of them, but there are a few instances where the pendant is a Device. I'd have to create a whole new custom field for this.

Database changes

No response

External dependencies

No response

Originally created by @Azmodeszer on GitHub (Mar 11, 2025). ### NetBox version v4.2.5 ### Feature type Change to existing functionality ### Proposed functionality Currently, when selecting the custom field type Object or Multiple objects, it's only possible to choose a single model under Related object type. Are there any hurdles with simply allowing multiple? ### Use case My personal use case is a custom field for linking to a test or production instance of a VM or device. I currently have the related object model set to Virtual Machine since that covers most of them, but there are a few instances where the pendant is a Device. I'd have to create a whole new custom field for this. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:36:58 +01:00
adam closed this issue 2025-12-29 21:36:58 +01:00
adam commented 2025-12-29 21:36:59 +01:00
Author
Owner
Copy Link

@bctiemann commented on GitHub (Mar 20, 2025):

Unfortunately this isn't something we can support with custom fields. This might be an opportunity for a custom plugin.

@bctiemann commented on GitHub (Mar 20, 2025): Unfortunately this isn't something we can support with custom fields. This might be an opportunity for a custom plugin.
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 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#10867
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?