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 fields don't distinguish "interface" and "vminterface" #4746

New Issue
Closed
opened 2025-12-29 19:20:04 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:20:04 +01:00
Owner
Copy Link

Originally created by @candlerb on GitHub (Apr 9, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v2.11 beta (beta.netbox.dev)

Python version

3.7

Steps to Reproduce

  1. Create a custom field on DCIM > Interface
  2. Create a custom field on Virtualization > Interface
  3. View the list of custom fields

Expected Behavior

You should be able to distinguish which custom fields are on "interface" and which are on "vminterface"

Observed Behavior

Both are displayed as "interface" - you have to edit each one to see what it's attached to.

Originally created by @candlerb on GitHub (Apr 9, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v2.11 beta (beta.netbox.dev) ### Python version 3.7 ### Steps to Reproduce 1. Create a custom field on DCIM > Interface 2. Create a custom field on Virtualization > Interface 3. View the list of custom fields ### Expected Behavior You should be able to distinguish which custom fields are on "interface" and which are on "vminterface" ### Observed Behavior Both are displayed as "interface" - you have to edit each one to see what it's attached to.
adam added the type: bugstatus: acceptedbeta labels 2025-12-29 19:20:04 +01:00
adam closed this issue 2025-12-29 19:20:04 +01:00
adam commented 2025-12-29 19:20:05 +01:00
Author
Owner
Copy Link

@candlerb commented on GitHub (Apr 9, 2021):

Screenshot:
image

The fields named "VM xxx" are actually on Virtualization > Interface

Of course, for this application I did it wrongly. I should have created a single custom field which relates to both interface and vminterface. But the issue about distinguishing the two types of "interface" still applies:

image

Relates to #5401

@candlerb commented on GitHub (Apr 9, 2021): Screenshot: ![image](https://user-images.githubusercontent.com/44789/114157056-22af1b80-991b-11eb-93ee-b2a8bd38ae9d.png) The fields named "VM xxx" are actually on Virtualization > Interface Of course, for this application I did it wrongly. I should have created a single custom field which relates to both interface and vminterface. But the issue about distinguishing the two types of "interface" still applies: ![image](https://user-images.githubusercontent.com/44789/114157604-b7197e00-991b-11eb-86b0-09fd2f1d961f.png) Relates to #5401
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 beta 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#4746
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?