Allow custom object fields to reference a user or group

[joaolucasmacedo]

NetBox version

v3.3.5

Feature type

Data model extension

Proposed functionality

Being able to create object type custom fields with Netbox users.

Use case

Being able to point a specific user which is responsible for a given object, like a device or VM.

Database changes

No response

External dependencies

No response

[bistraque]

That's why Contacts are for: give a specific role to a specific contact for a given object, and for free you get a many-to-many relationship. In case an object does not have a Contacts field, a custom field of that type will do. It also allows for Contacts to exist while not being Users with credentials on Netbox itself (covers different tenancy models).

Arguably, we may question the use case where a Contact is optionally associated with a Netbox User at creation time (e.g. autofill name and associated info). This could be helpful as a "garbage collection" strategy to detect obsolete contact info (via scripting for example if user no longer valid in ldap).

[jeremystretch]

I think it's reasonable to allow referencing a NetBox user (or group) as well; we do this today with rack reservations.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

[abhi1693]

Can I take a shot at this?

[jeremystretch]

Assigned to you @abhi1693, thanks!

[abhi1693]

For the assigned user/group, should the custom field be hidden from the UI that were not assigned on it?

[jeremystretch]

@abhi1693, sorry, I'm not clear on what you're asking. Could you give me an example?

[abhi1693]

Lets say I created a custom field and assigned to bob. Should the field only be visible to bob whether its view or edit on the UI? If so, should this also be tackled on the API side?

[jeremystretch]

No, I don't think so. I believe the intent here is merely to be able to associate an arbitrary object with a particular user or group, like we do currently for rack reservations.