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

Drop contact_* fields from dcim.Site #5612

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

Originally created by @jeremystretch on GitHub (Nov 4, 2021).

Originally assigned to: @jeremystretch on GitHub.

Proposed Changes

Remove the following fields from the dcim.Site model:

  • contact_name
  • contact_phone
  • contact_email

Justification

NetBox v3.1 introduced a new Contact model (see #1344), which supports the more efficient assignment of contacts to sites and other objects, obviating the need for these fields on the model.

Originally created by @jeremystretch on GitHub (Nov 4, 2021). Originally assigned to: @jeremystretch on GitHub. ### Proposed Changes Remove the following fields from the dcim.Site model: * `contact_name` * `contact_phone` * `contact_email` ### Justification NetBox v3.1 introduced a new Contact model (see #1344), which supports the more efficient assignment of contacts to sites and other objects, obviating the need for these fields on the model.
adam added the status: acceptedtype: deprecation labels 2025-12-29 19:30:09 +01:00
adam closed this issue 2025-12-29 19:30:09 +01:00
adam commented 2025-12-29 19:30:09 +01:00
Author
Owner
Copy Link

@cs-1 commented on GitHub (Nov 5, 2021):

Will the upgrade script migrate existing contacts from sites to the new Contact model?

@cs-1 commented on GitHub (Nov 5, 2021): Will the upgrade script migrate existing contacts from sites to the new Contact model?
adam commented 2025-12-29 19:30:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 5, 2021):

I wasn't comfortable including an automatic migration for existing contact data, given the largely free-form nature of the fields. However, we could publish a script to take care of this for users. It would allow users to perform a "dry-run" before committing the new objects.

@jeremystretch commented on GitHub (Nov 5, 2021): I wasn't comfortable including an automatic migration for existing contact data, given the largely free-form nature of the fields. However, we could publish a script to take care of this for users. It would allow users to perform a "dry-run" before committing the new objects.
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: accepted type: deprecation
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#5612
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?