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

Image being reference to several objects #7014

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

Originally created by @jcralbino on GitHub (Sep 22, 2022).

NetBox version

v3.3.4

Feature type

Change to existing functionality

Proposed functionality

Currently we are able to upload an image to several data models, namely to Site, Locations for example.

What i propose is that we enable the option to be able to reference the same image to several objects.

Use case

When documenting for example the building layout we can do the following:

Site : BuildingA-: Represents Building-A -> Image uploaded can represent the building.
Location: Floor-0-BLDA -> Parent is BuildingA : Used Represents Building-A
-> Image ImgFloor0: uploaded represents the floorplan in that building.
Location: Room00SG10 -> Parent is Floor-0-BLDA: Usedto represent a room in level 0 in Building-A
-> Image Room00SG10: uploaded represents details in the room of that building.

If we can reference previous uploaded images, here we could add additional images in Location "Room00SG10 " refering for example the ImgFloor0 and Room00SG10, within the Location Room00SG10 .

This way we will have all the details needed within one page, not requiring to browse to different places.

Database changes

Create a table for Uploaded images that references the uploaded and with the locations where they should be viewed.

External dependencies

none

Originally created by @jcralbino on GitHub (Sep 22, 2022). ### NetBox version v3.3.4 ### Feature type Change to existing functionality ### Proposed functionality Currently we are able to upload an image to several data models, namely to Site, Locations for example. What i propose is that we enable the option to be able to reference the same image to several objects. ### Use case When documenting for example the building layout we can do the following: Site : BuildingA-: Represents Building-A -> Image uploaded can represent the building. Location: Floor-0-BLDA -> Parent is BuildingA : Used Represents Building-A -> Image ImgFloor0: uploaded represents the floorplan in that building. Location: Room00SG10 -> Parent is Floor-0-BLDA: Usedto represent a room in level 0 in Building-A -> Image Room00SG10: uploaded represents details in the room of that building. If we can reference previous uploaded images, here we could add additional images in Location "Room00SG10 " refering for example the ImgFloor0 and Room00SG10, within the Location Room00SG10 . This way we will have all the details needed within one page, not requiring to browse to different places. ### Database changes Create a table for Uploaded images that references the uploaded and with the locations where they should be viewed. ### External dependencies none
adam added the type: featurepending closure labels 2025-12-29 19:47:52 +01:00
adam closed this issue 2025-12-29 19:47:53 +01:00
adam commented 2025-12-29 19:47:53 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 26, 2022):

It sounds like perhaps you have more complex requirements than what NetBox's image attachment feature is intended to serve. You're likely better off using a general purpose external file store and linking NetBox objects to it.

@jeremystretch commented on GitHub (Sep 26, 2022): It sounds like perhaps you have more complex requirements than what NetBox's image attachment feature is intended to serve. You're likely better off using a general purpose external file store and linking NetBox objects to it.
adam commented 2025-12-29 19:47:53 +01:00
Author
Owner
Copy Link

@jcralbino commented on GitHub (Oct 3, 2022):

I believe that this is not the only use case where a user can upload the same image to more objects

I understand that netbox is not meant to store documents, but the way it handles images can be improved. This seems a feature that is quite useful for several reasons

@jcralbino commented on GitHub (Oct 3, 2022): I believe that this is not the only use case where a user can upload the same image to more objects I understand that netbox is not meant to store documents, but the way it handles images can be improved. This seems a feature that is quite useful for several reasons
adam commented 2025-12-29 19:47:54 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 3, 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 (Dec 3, 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:47:54 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 2, 2023):

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 (Jan 2, 2023): 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 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#7014
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?