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

Custom fields for Users #7076

New Issue
Closed
opened 2025-12-29 20:18:56 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:18:56 +01:00
Owner
Copy Link

Originally created by @PieterL75 on GitHub (Oct 5, 2022).

NetBox version

v3.3.0

Feature type

Change to existing functionality

Proposed functionality

Custom fields are currently supported for Netbox Models.
Can this be extended to Users also

Use case

We have now a situation where we would like to store custom data on a user object.
This additional data is only related to that Used and not to any objects they create.

This additional account data, is required for API integrations in webhooks.

Database changes

Probably need to extend the Djange User Model with customfieldmixin

External dependencies

No response

Originally created by @PieterL75 on GitHub (Oct 5, 2022). ### NetBox version v3.3.0 ### Feature type Change to existing functionality ### Proposed functionality Custom fields are currently supported for Netbox Models. Can this be extended to Users also ### Use case We have now a situation where we would like to store custom data on a user object. This additional data is only related to that Used and not to any objects they create. This additional account data, is required for API integrations in webhooks. ### Database changes Probably need to extend the Djange User Model with customfieldmixin ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 20:18:56 +01:00
adam closed this issue 2025-12-29 20:18:57 +01:00
adam commented 2025-12-29 20:18:57 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 18, 2022):

Can this be extended to Users also

We're not able to easily extend the built-in Django User model without a fairly disruptive migration to a custom user model, unfortunately. Instead, the recommended approach would be to write a plugin that introduces a model to hold the desired data and its relation to a NetBox user.

@jeremystretch commented on GitHub (Oct 18, 2022): > Can this be extended to Users also We're not able to easily extend the built-in Django User model without a fairly disruptive migration to a custom user model, unfortunately. Instead, the recommended approach would be to write a plugin that introduces a model to hold the desired data and its relation to a NetBox user.
adam commented 2025-12-29 20:18:57 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 18, 2022):

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[bot] commented on GitHub (Dec 18, 2022): 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](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:18:57 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 17, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jan 17, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure 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#7076
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?