Add Contact Assignment support to Virtual Circuits #395

New Issue

MrUnknownDE · 2026-04-05T16:29:19+02:00

MrUnknownDE commented

2026-04-05 16:29:19 +02:00

Originally created by @Andres1357 on 2/9/2026

NetBox version

v4.5.2

Feature type

New functionality

Proposed functionality

Proposing to add the same level of support for Contacts to the Virtual Circuit model as for physical Circuits, and other models.

Currently the Virtual Circuit page is missing the Contacts tab

Present on physical Circuit page

This may be a UI change as well as a change to backend validation. I attempted to create a contact assignment for a virtual circuit through API and got a 400.
POST https://your.netbox.com/api/tenancy/contact-assignments/
Body:

{
  "object_type": "circuits.virtualcircuit",
  "object_id": 1,
  "contact": 3,
  "role": 1
}

Response: 400 Bad Request

{
  "__all__": [
    "Contacts cannot be assigned to this object type (Circuits | virtual circuit)."
  ]
}

Use case

We provide circuits to customers and use contacts in NetBox circuits to track important contacts at the customer org for maintenance notifications, etc. For virtual circuits, we've had to resort to adding a custom field to track these contacts. Would love to have virtual circuits take advantage of the built-in contacts features.

Database changes

No new models or fields.

External dependencies

No response

*Originally created by @Andres1357 on 2/9/2026* ### NetBox version v4.5.2 ### Feature type New functionality ### Proposed functionality Proposing to add the same level of support for Contacts to the Virtual Circuit model as for physical Circuits, and other models. Currently the Virtual Circuit page is missing the Contacts tab <img width="459" height="292" alt="Image" src="https://github.com/user-attachments/assets/334cbe2e-a5fd-4213-b6ce-6d78f88f193d" /> Present on physical Circuit page <img width="632" height="413" alt="Image" src="https://github.com/user-attachments/assets/a5916687-c461-4591-80ac-9965c16e6993" /> This may be a UI change as well as a change to backend validation. I attempted to create a contact assignment for a virtual circuit through API and got a 400. POST https://your.netbox.com/api/tenancy/contact-assignments/ Body: ``` { "object_type": "circuits.virtualcircuit", "object_id": 1, "contact": 3, "role": 1 } ``` Response: 400 Bad Request ``` { "__all__": [ "Contacts cannot be assigned to this object type (Circuits | virtual circuit)." ] } ``` ### Use case We provide circuits to customers and use contacts in NetBox circuits to track important contacts at the customer org for maintenance notifications, etc. For virtual circuits, we've had to resort to adding a custom field to track these contacts. Would love to have virtual circuits take advantage of the built-in contacts features. ### Database changes No new models or fields. ### External dependencies _No response_

MrUnknownDE closed this issue

2026-04-05 16:29:19 +02:00

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

No Label complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#395