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

Introduce a mechanism for storing individual user preferences #2697

New Issue
Closed
opened 2025-12-29 18:21:10 +01:00 by adam · 0 comments
adam commented 2025-12-29 18:21:10 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Jun 24, 2019).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.6.8
  • NetBox version: 2.6.0

Proposed Functionality

Introduce a model for storing the preferences of an individual user. A simple model providing arbitrary JSON data storage associated one-to-one with user accounts is probably sufficient. This will allow a user to set a preferred item (e.g. the default status for new prefixes) that will persist indefinitely.

Use Case

This has been highlighted as a requirement for several other features:

  • #492 - Customized table column ordering
  • #1426 - Customized default statuses

Database Changes

Introduce a new model under the users app, e.g. UserPreferences.

External Dependencies

None

Originally created by @jeremystretch on GitHub (Jun 24, 2019). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 3.6.8 * NetBox version: 2.6.0 ### Proposed Functionality Introduce a model for storing the preferences of an individual user. A simple model providing arbitrary JSON data storage associated one-to-one with user accounts is probably sufficient. This will allow a user to set a preferred item (e.g. the default status for new prefixes) that will persist indefinitely. ### Use Case This has been highlighted as a requirement for several other features: * #492 - Customized table column ordering * #1426 - Customized default statuses ### Database Changes Introduce a new model under the `users` app, e.g. `UserPreferences`. ### External Dependencies None
adam added the status: accepted label 2025-12-29 18:21:10 +01:00
adam closed this issue 2025-12-29 18:21:10 +01:00
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
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#2697
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?