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

Select previously-uploaded photo to attach to another device #5615

New Issue
Closed
opened 2025-12-29 19:30:10 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:30:10 +01:00
Owner
Copy Link

Originally created by @danfiscus on GitHub (Nov 4, 2021).

NetBox version

v3.0.8

Feature type

Change to existing functionality

Proposed functionality

When uploading a photo to attach to a device, I would like to have the option to select a photo which I have already uploaded and reuse it for another device. This functionality could be further expanded by presenting users the option to select multiple photos at a time to attach, and/or to filter the list of previously uploaded photos by recency or whether the photo was uploaded to another device within the same rack.
Alternatively, this idea could be expressed as sharing the same image between multiple devices, but not between an entire rack.

Use case

We like to store images of the devices in our rack, but to save time we take photos of a few U at a time and upload the same photo to each device in that section of the rack. Unfortunately right now, attaching the same exact photo means re-uploading the image a second time, rather than being able to select from a list of photos uploaded in the past. Being able to attach the same photo multiple times without uploading and storing it separately saves storage space and reduces the time to attach images to entities in some cases.

Database changes

No response

External dependencies

No response

Originally created by @danfiscus on GitHub (Nov 4, 2021). ### NetBox version v3.0.8 ### Feature type Change to existing functionality ### Proposed functionality When uploading a photo to attach to a device, I would like to have the option to select a photo which I have already uploaded and reuse it for another device. This functionality could be further expanded by presenting users the option to select multiple photos at a time to attach, and/or to filter the list of previously uploaded photos by recency or whether the photo was uploaded to another device within the same rack. Alternatively, this idea could be expressed as sharing the same image between multiple devices, but not between an entire rack. ### Use case We like to store images of the devices in our rack, but to save time we take photos of a few U at a time and upload the same photo to each device in that section of the rack. Unfortunately right now, attaching the same exact photo means re-uploading the image a second time, rather than being able to select from a list of photos uploaded in the past. Being able to attach the same photo multiple times without uploading and storing it separately saves storage space and reduces the time to attach images to entities in some cases. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:30:10 +01:00
adam closed this issue 2025-12-29 19:30:10 +01:00
adam commented 2025-12-29 19:30:11 +01:00
Author
Owner
Copy Link

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

The ImageAttachment model associates a unique uploaded image with each instance, which aren't intended for reuse among multiple objects. For what you're describing, you're probably better off linking to an externally hosted image.

@jeremystretch commented on GitHub (Nov 5, 2021): The ImageAttachment model associates a unique uploaded image with each instance, which aren't intended for reuse among multiple objects. For what you're describing, you're probably better off linking to an externally hosted image.
adam commented 2025-12-29 19:30:11 +01:00
Author
Owner
Copy Link

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

I'm going to decline this proposal for a few reasons:

  1. Supporting the reuse of an attachment for multiple objects greatly complicates the existing data model.
  2. It's fair to assume this would be a pretty infrequent requirement.
  3. A reasonable workaround would be to link to image attachments from within the comment fields of other objects.
@jeremystretch commented on GitHub (Nov 11, 2021): I'm going to decline this proposal for a few reasons: 1. Supporting the reuse of an attachment for multiple objects greatly complicates the existing data model. 2. It's fair to assume this would be a pretty infrequent requirement. 3. A reasonable workaround would be to link to image attachments from within the comment fields of other objects.
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 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#5615
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?