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

set the journal-entry timestamp with the API #6620

New Issue
Closed
opened 2025-12-29 19:43:13 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:43:13 +01:00
Owner
Copy Link

Originally created by @brammeleman on GitHub (Jul 1, 2022).

NetBox version

v3.2.5

Feature type

Change to existing functionality

Proposed functionality

Set the date/time-stamp for new journal entries with the API.

Use case

For migrating log/journal entries from another DCIM.

Database changes

No changes

External dependencies

No response

Originally created by @brammeleman on GitHub (Jul 1, 2022). ### NetBox version v3.2.5 ### Feature type Change to existing functionality ### Proposed functionality Set the date/time-stamp for new journal entries with the API. ### Use case For migrating log/journal entries from another DCIM. ### Database changes No changes ### External dependencies _No response_
adam added the type: featurepending closurestatus: under review labels 2025-12-29 19:43:13 +01:00
adam closed this issue 2025-12-29 19:43:13 +01:00
adam commented 2025-12-29 19:43:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 27, 2022):

Set the date/time-stamp for new journal entries with the API.

This does not seem like something we want to expose in the REST API, as it opens the door for users to fabricate the creation times of journal entries.

@jeremystretch commented on GitHub (Jul 27, 2022): > Set the date/time-stamp for new journal entries with the API. This does not seem like something we want to expose in the REST API, as it opens the door for users to fabricate the creation times of journal entries.
adam commented 2025-12-29 19:43:14 +01:00
Author
Owner
Copy Link

@brammeleman commented on GitHub (Jul 28, 2022):

I understand your concern.
Personally, as I just completed the migration from our old dcim to Netbox, I don't need this feature anymore. Except for the journal, I was able to do a pure API based import of all data. The journal entries (~2k) where inserted directly into the database, which is just a bit more work/complicated.

pros:

  • beneficial for new Netbox users migrating from another dcim (no need to write to the database directly)

cons:

  • special (admin) permission needed to back date and impersonate journal entry creation
  • maybe too much work for a one-time import scenario
@brammeleman commented on GitHub (Jul 28, 2022): I understand your concern. Personally, as I just completed the migration from our old dcim to Netbox, I don't need this feature anymore. Except for the journal, I was able to do a pure API based import of all data. The journal entries (~2k) where inserted directly into the database, which is just a bit more work/complicated. pros: - beneficial for new Netbox users migrating from another dcim (no need to write to the database directly) cons: - special (admin) permission needed to back date and impersonate journal entry creation - maybe too much work for a one-time import scenario
adam commented 2025-12-29 19:43:14 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 27, 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 (Sep 27, 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 19:43:14 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 28, 2022):

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 (Oct 28, 2022): 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 status: under review 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#6620
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?