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 assignment for custom fields similar to config contexts #8888

New Issue
Closed
opened 2025-12-29 20:42:31 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:42:31 +01:00
Owner
Copy Link

Originally created by @TribuneX on GitHub (Nov 28, 2023).

NetBox version

v3.6.3

Feature type

New functionality

Proposed functionality

Allow to add assignments to custom fields (similar to the assignment in config contexts)

Might be dependent on the refactoring planned in https://github.com/netbox-community/netbox/issues/14000

Use case

We created a custom field for interfaces, which should only be available on interfaces which are part of a virtual chassis with a certain device type.
Therefore, we would like to add an assignment to this custom field similar to assignments available on config contexts.

This is the UI available for config contexts, which could look similar in custom fields:
Screenshot 2023-11-28 at 11 58 39

Database changes

No response

External dependencies

No response

Originally created by @TribuneX on GitHub (Nov 28, 2023). ### NetBox version v3.6.3 ### Feature type New functionality ### Proposed functionality Allow to add assignments to custom fields (similar to the assignment in config contexts) Might be dependent on the refactoring planned in https://github.com/netbox-community/netbox/issues/14000 ### Use case We created a custom field for interfaces, which should only be available on interfaces which are part of a virtual chassis with a certain device type. Therefore, we would like to add an assignment to this custom field similar to assignments available on config contexts. This is the UI available for config contexts, which could look similar in custom fields: <img width="766" alt="Screenshot 2023-11-28 at 11 58 39" src="https://github.com/netbox-community/netbox/assets/7440759/5d814988-d366-4780-882c-8c833c513c22"> ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: duplicate labels 2025-12-29 20:42:31 +01:00
adam closed this issue 2025-12-29 20:42:31 +01:00
adam commented 2025-12-29 20:42:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 28, 2023):

Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #11367 for further discussion.

@jeremystretch commented on GitHub (Nov 28, 2023): Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #11367 for further discussion.
adam commented 2025-12-29 20:42:32 +01:00
Author
Owner
Copy Link

@TribuneX commented on GitHub (Nov 28, 2023):

Thanks for the reference. I am wondering why config contexts are allowed to be assigned to certain types but custom fields should not be. Thats not part of the linked discussion yet.
Building a plugin just for a single extra field introduces a lot of overhead for just little functionality.

@TribuneX commented on GitHub (Nov 28, 2023): Thanks for the reference. I am wondering why config contexts are allowed to be assigned to certain types but custom fields should not be. Thats not part of the linked discussion yet. Building a plugin just for a single extra field introduces a lot of overhead for just little functionality.
adam commented 2025-12-29 20:42:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 28, 2023):

I think you misunderstand how config contexts work: Their values not defined per-object, whereas custom field values are. They are entirely separate concepts and used very differently.

@jeremystretch commented on GitHub (Nov 28, 2023): I think you misunderstand how config contexts work: Their values not defined per-object, whereas custom field values are. They are entirely separate concepts and used very differently.
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: duplicate 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#8888
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?