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

Bulk import of Journal entries ignore specified user #8589

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

Originally created by @Kage1 on GitHub (Sep 7, 2023).

NetBox version

v3.5.8

Python version

3.10

Steps to Reproduce

  1. Goto Operations - Journal Entries
  2. Select import
  3. Enter headers including "created_by"
  4. Fill out data to import including ID of the user to create the entry as
    4a. The user exists as an admin in organization
  5. Submit the import with auto-detect format
  6. The journal entry is created on the dcim.device but the user who created it is me vs the specified user.

Expected Behavior

The journal entry should be created and show it was the other user.

Observed Behavior

The journal entry is created by my user.

Originally created by @Kage1 on GitHub (Sep 7, 2023). ### NetBox version v3.5.8 ### Python version 3.10 ### Steps to Reproduce 1. Goto Operations - Journal Entries 2. Select import 3. Enter headers including "created_by" 4. Fill out data to import including ID of the user to create the entry as 4a. The user exists as an admin in organization 5. Submit the import with auto-detect format 6. The journal entry is created on the dcim.device but the user who created it is me vs the specified user. ### Expected Behavior The journal entry should be created and show it was the other user. ### Observed Behavior The journal entry is created by my user.
adam added the type: bugstatus: revisions needed labels 2025-12-29 20:38:31 +01:00
adam closed this issue 2025-12-29 20:38:31 +01:00
adam commented 2025-12-29 20:38:32 +01:00
Author
Owner
Copy Link

@pv2b commented on GitHub (Sep 8, 2023):

I'm unable to reproduce this on 3.6.1. I tried this in the demo instance:

assigned_object_type,assigned_object_id,kind,comments,created_by
dcim.device,108,danger,will robinson,2

And it created the journal entry by user number 2 (which in this case is "alice").

My guess was that maybe you accidentally entered the username (e.g. alice) instead of the user's ID (e.g. 2)? But this makes no sense because then you'll just get a validation error on import, you won't get a successful import like that.

Can you please clarify the exact CSV used for import? For example, make sure your headers are spelled correctly, including being all-lowercase. Unrecognized headers will be ignored. And also, if possible, try out your use case on the latest version of NetBox, optionally through the demo site at https://demo.netbox.dev/ which might be easier for you than upgrading.

@pv2b commented on GitHub (Sep 8, 2023): I'm unable to reproduce this on 3.6.1. I tried this in the demo instance: ``` assigned_object_type,assigned_object_id,kind,comments,created_by dcim.device,108,danger,will robinson,2 ``` And it created the journal entry by user number 2 (which in this case is "alice"). My guess was that maybe you accidentally entered the username (e.g. `alice`) instead of the user's ID (e.g. 2)? But this makes no sense because then you'll just get a validation error on import, you won't get a successful import like that. Can you please clarify the exact CSV used for import? For example, make sure your headers are spelled correctly, including being all-lowercase. Unrecognized headers will be ignored. And also, if possible, try out your use case on the latest version of NetBox, optionally through the demo site at https://demo.netbox.dev/ which might be easier for you than upgrading.
adam commented 2025-12-29 20:38:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 8, 2023):

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

@jeremystretch commented on GitHub (Sep 8, 2023): Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.
adam commented 2025-12-29 20:38:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 21, 2023):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@jeremystretch commented on GitHub (Sep 21, 2023): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
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: revisions needed type: bug
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#8589
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?