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

Extend the default "created" field on models from DateField to DateTimeField #6006

New Issue
Closed
opened 2025-12-29 19:35:38 +01:00 by adam · 0 comments
adam commented 2025-12-29 19:35:38 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Jan 26, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.1.6

Feature type

Change to existing functionality

Proposed functionality

All change-logged models in NetBox have two common fields:

created = models.DateField(auto_now_add=True)
last_updated = models.DateTimeField(auto_now=True)

This issue proposes migrating the created field to a DateTimeField to match last_updated. (In doing so, existing date values will receive a 00:00:00 timestamp.)

Use case

Provides greater granularity concerning the time at which an object in NetBox is created.

Database changes

Simple migration of the created field on all relevant models.

External dependencies

No response

Originally created by @jeremystretch on GitHub (Jan 26, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.1.6 ### Feature type Change to existing functionality ### Proposed functionality All change-logged models in NetBox have two common fields: ``` created = models.DateField(auto_now_add=True) last_updated = models.DateTimeField(auto_now=True) ``` This issue proposes migrating the `created` field to a DateTimeField to match `last_updated`. (In doing so, existing date values will receive a 00:00:00 timestamp.) ### Use case Provides greater granularity concerning the time at which an object in NetBox is created. ### Database changes Simple migration of the `created` field on all relevant models. ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:35:38 +01:00
adam closed this issue 2025-12-29 19:35:38 +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 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#6006
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?