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

Uploading / Deleting / Editing images does not generate a change log #5655

New Issue
Closed
opened 2025-12-29 19:30:42 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:30:42 +01:00
Owner
Copy Link

Originally created by @jasonyates on GitHub (Nov 12, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

3.0.9

Python version

3.8

Steps to Reproduce

Upload / edit or delete an image associated with a rack, site or location. No change log entry is generated.

I am using S3 storage for images, I have not tested if change logs are generated when using other storage methods.

Expected Behavior

A change log item is generated for adding, modifying or deleting an image.

Observed Behavior

No change log is generated.

Originally created by @jasonyates on GitHub (Nov 12, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version 3.0.9 ### Python version 3.8 ### Steps to Reproduce Upload / edit or delete an image associated with a rack, site or location. No change log entry is generated. I am using S3 storage for images, I have not tested if change logs are generated when using other storage methods. ### Expected Behavior A change log item is generated for adding, modifying or deleting an image. ### Observed Behavior No change log is generated.
adam added the status: acceptedtype: feature labels 2025-12-29 19:30:42 +01:00
adam closed this issue 2025-12-29 19:30:42 +01:00
adam commented 2025-12-29 19:30:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 17, 2021):

While I think it's fair to approach this as a bug, I'm going to treat it as a feature request primarily because the resolution involves modifying the ImageAttachment class to inherit from ChangeLoggedModel, which introduces a new field (last_updated). Also for this reason, I'm going to implement this within the feature branch for v3.1.

@jeremystretch commented on GitHub (Nov 17, 2021): While I think it's fair to approach this as a bug, I'm going to treat it as a feature request primarily because the resolution involves modifying the ImageAttachment class to inherit from ChangeLoggedModel, which introduces a new field (`last_updated`). Also for this reason, I'm going to implement this within the `feature` branch for v3.1.
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#5655
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?