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

Link Providers NOC & Admin Contact to a Contact object #5880

New Issue
Closed
opened 2025-12-29 19:33:46 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:33:46 +01:00
Owner
Copy Link

Originally created by @jasonyates on GitHub (Jan 5, 2022).

NetBox version

3.1.2

Feature type

New functionality

Proposed functionality

The Circuit Providers model has the ability to manually enter a NOC & Admin contact and also the ability to associate Contact objects.

It would be useful to re-use the contact objects and be able to associate them directly to a NOC and Admin contact of a provider as opposed to NOC & Admin being freeform text.

Use case example, Equinix are a provider of a site (i.e. Colo Space) and a Circuit (i.e Equinix Connect DIA). I have an Equinix NOC Contact created and associated to the site however I cannot use that same NOC Contact in the provider as "NOC Contact" is a freeform text box.

Use case

Allows for more efficient re-use of Contact objects and reduction of data duplication. One place to manage NOC & Admin contacts.

Database changes

No response

External dependencies

No response

Originally created by @jasonyates on GitHub (Jan 5, 2022). ### NetBox version 3.1.2 ### Feature type New functionality ### Proposed functionality The Circuit Providers model has the ability to manually enter a NOC & Admin contact and also the ability to associate Contact objects. It would be useful to re-use the contact objects and be able to associate them directly to a NOC and Admin contact of a provider as opposed to NOC & Admin being freeform text. Use case example, Equinix are a provider of a site (i.e. Colo Space) and a Circuit (i.e Equinix Connect DIA). I have an Equinix NOC Contact created and associated to the site however I cannot use that same NOC Contact in the provider as "NOC Contact" is a freeform text box. ### Use case Allows for more efficient re-use of Contact objects and reduction of data duplication. One place to manage NOC & Admin contacts. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:33:46 +01:00
adam closed this issue 2025-12-29 19:33:46 +01:00
adam commented 2025-12-29 19:33:46 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jan 5, 2022):

I think instead of linking, as providers are able to hold contact objects, this should be a deprecation of the NOC contact and Admin contact fields.

@DanSheps commented on GitHub (Jan 5, 2022): I think instead of linking, as providers are able to hold contact objects, this should be a deprecation of the NOC contact and Admin contact fields.
adam commented 2025-12-29 19:33:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 7, 2022):

As of v3.2.0 it's now possible to assign contacts (and their corresponding role & priority) to a provider, which I believe addresses the use case here.

As #9046 has been opened to deprecate the provider model's built-in contact fields, I'll go ahead and close this out.

@jeremystretch commented on GitHub (Apr 7, 2022): As of v3.2.0 it's now possible to assign contacts (and their corresponding role & priority) to a provider, which I believe addresses the use case here. As #9046 has been opened to deprecate the provider model's built-in contact fields, I'll go ahead and close this out.
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 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#5880
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?