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 Users to be used as Contact #11156

New Issue
Closed
opened 2025-12-29 21:41:06 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:41:06 +01:00
Owner
Copy Link

Originally created by @peterbaumert on GitHub (May 9, 2025).

NetBox version

v4.3.0

Feature type

Data model extension

Proposed functionality

I would like to be able to assign users as Contacts, so I don't have to duplicate most of the data that is available already at the User anyway.

Use case

Not needing to duplicate User/Contact data just for the sake of being able to assign Contacts.

Database changes

Probably the relationship part between the contact asignment and the contact/user model.

External dependencies

I don't think there are any.

Originally created by @peterbaumert on GitHub (May 9, 2025). ### NetBox version v4.3.0 ### Feature type Data model extension ### Proposed functionality I would like to be able to assign users as Contacts, so I don't have to duplicate most of the data that is available already at the User anyway. ### Use case Not needing to duplicate User/Contact data just for the sake of being able to assign Contacts. ### Database changes Probably the relationship part between the contact asignment and the contact/user model. ### External dependencies I don't think there are any.
adam added the type: feature label 2025-12-29 21:41:06 +01:00
adam closed this issue 2025-12-29 21:41:06 +01:00
adam commented 2025-12-29 21:41:06 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (May 29, 2025):

This would really mess up the data model to support both. You can create a custom field on a contact with type object and related object type of User that may get the related information that you want.

@arthanson commented on GitHub (May 29, 2025): This would really mess up the data model to support both. You can create a custom field on a contact with type object and related object type of User that may get the related information that you want.
adam commented 2025-12-29 21:41:07 +01:00
Author
Owner
Copy Link

@peterbaumert commented on GitHub (May 29, 2025):

@arthanson I can understand that. The workaround you suggest still would duplicate a lot of the data though since Contact has required fields too.

Opening Contacts to be User would also probably make it possible to use it to assign rights. Like if User has Owner role he can edit and so on.

@peterbaumert commented on GitHub (May 29, 2025): @arthanson I can understand that. The workaround you suggest still would duplicate a lot of the data though since Contact has required fields too. Opening Contacts to be User would also probably make it possible to use it to assign rights. Like if User has Owner role he can edit and so on.
adam commented 2025-12-29 21:41:07 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 7, 2025):

We intentionally maintain strict separation between the objects in NetBox and the users who make changes to those objects, for various reasons. Unfortunately the proposed functionality would violate that separation, so we have to decline it.

@jeremystretch commented on GitHub (Aug 7, 2025): We intentionally maintain strict separation between the objects in NetBox and the users who make changes to those objects, for various reasons. Unfortunately the proposed functionality would violate that separation, so we have to decline it.
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#11156
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?