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

Custom field type object 2way visibility #8114

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

Originally created by @kirillmuravyev on GitHub (May 25, 2023).

NetBox version

v3.5.2

Feature type

Data model extension

Proposed functionality

Hi All.
I was playing with custom fields a little bit and noticed interesting thing that might be useful to implement.
I have creates a custom field with type "object" in "dcim -> device", object type is "virtual machine".
So I want to link some devices to virtual machines.
BTW, there is no way to model virtual network devices deployed on cloud VMs, when you have a virtual machine in cloud and network device software deployed on it. And we treat those things differently, vurtual machine itself is supported by one team, but virtual network device installed on that machine is supported by another team.
That is why I want to link device and virtual machine together.

So, when I did the above relation, I can open device and link it to virtual machine, but from the virtual machine perspective I do not see that relation.

I think would be good to see that relation automatically if I reference object in custom field. Otherwise you have to create 2 custom fields and maintain them in order to track it from both sides

Use case

Ability to see that specific instance of object is referenced by another one with custom field.

Database changes

No response

External dependencies

No response

Originally created by @kirillmuravyev on GitHub (May 25, 2023). ### NetBox version v3.5.2 ### Feature type Data model extension ### Proposed functionality Hi All. I was playing with custom fields a little bit and noticed interesting thing that might be useful to implement. I have creates a custom field with type "object" in "dcim -> device", object type is "virtual machine". So I want to link some devices to virtual machines. BTW, there is no way to model virtual network devices deployed on cloud VMs, when you have a virtual machine in cloud and network device software deployed on it. And we treat those things differently, vurtual machine itself is supported by one team, but virtual network device installed on that machine is supported by another team. That is why I want to link device and virtual machine together. So, when I did the above relation, I can open device and link it to virtual machine, but from the virtual machine perspective I do not see that relation. I think would be good to see that relation automatically if I reference object in custom field. Otherwise you have to create 2 custom fields and maintain them in order to track it from both sides ### Use case Ability to see that specific instance of object is referenced by another one with custom field. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 20:32:36 +01:00
adam closed this issue 2025-12-29 20:32:36 +01:00
adam commented 2025-12-29 20:32:37 +01:00
Author
Owner
Copy Link

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

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (May 25, 2023): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 20:32:38 +01:00
Author
Owner
Copy Link

@kirillmuravyev commented on GitHub (May 25, 2023):

I will convert it to discussion at this point to clarify with community if it worth creating a feature.
Thank you!

@kirillmuravyev commented on GitHub (May 25, 2023): I will convert it to discussion at this point to clarify with community if it worth creating a feature. Thank you!
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: 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#8114
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?