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

Adding Assignment to Custom Field #10406

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

Originally created by @remchuk on GitHub (Oct 25, 2024).

NetBox version

v3.5.6

Feature type

New functionality

Triage priority

N/A

Proposed functionality

Adding assignment to custom field.
It doesn't have to be a required field but it could help a lot of people.

I want to have the option to link 2 custom field.
Meaning I would like to have 2 custom fields, which one is assigned to other,
it will act as "is_primary" in the IPAM --> IP Addresses. and "Primary IPv4" in DCIM --> Devices.

Currently there is no real option to do this, and developing a plugin for this fills like a huge overkill.
Is there a reason for not having this?

Use case

Currently I have to model each of those "custom fields" by it self.

I have for example a custom field called vpc_pair, I think it is a waste of time and quite uncomfortable to add it on each device, rather then if I would have added it to one of them, the other would also be changed.

Database changes

No response

External dependencies

No response

Originally created by @remchuk on GitHub (Oct 25, 2024). ### NetBox version v3.5.6 ### Feature type New functionality ### Triage priority N/A ### Proposed functionality Adding assignment to custom field. It doesn't have to be a required field but it could help a lot of people. I want to have the option to link 2 custom field. Meaning I would like to have 2 custom fields, which one is assigned to other, it will act as "is_primary" in the IPAM --> IP Addresses. and "Primary IPv4" in DCIM --> Devices. Currently there is no real option to do this, and developing a plugin for this fills like a huge overkill. Is there a reason for not having this? ### Use case Currently I have to model each of those "custom fields" by it self. I have for example a custom field called `vpc_pair`, I think it is a waste of time and quite uncomfortable to add it on each device, rather then if I would have added it to one of them, the other would also be changed. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurenetbox labels 2025-12-29 21:31:02 +01:00
adam closed this issue 2025-12-29 21:31:03 +01:00
adam commented 2025-12-29 21:31:03 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 6, 2025):

I have for example a custom field called vpc_pair, I think it is a waste of time and quite uncomfortable to add it on each device, rather then if I would have added it to one of them, the other would also be changed.

Custom fields are intended to store unique values per object. It sounds like you're trying to use them to represent a single related object, which is not supported. (You might consider writing a plugin to support your use case.)

@jeremystretch commented on GitHub (Feb 6, 2025): > I have for example a custom field called vpc_pair, I think it is a waste of time and quite uncomfortable to add it on each device, rather then if I would have added it to one of them, the other would also be changed. Custom fields are intended to store unique values _per object_. It sounds like you're trying to use them to represent a single _related_ object, which is not supported. (You might consider writing a plugin to support your use case.)
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 netbox 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#10406
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?