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

Add the ability to see images assigned to subobjects #8908

New Issue
Closed
opened 2025-12-29 20:42:43 +01:00 by adam · 10 comments
adam commented 2025-12-29 20:42:43 +01:00
Owner
Copy Link

Originally created by @drobnymichal on GitHub (Dec 3, 2023).

NetBox version

v3.6.5

Feature type

New functionality

Proposed functionality

We would like to add the ability to view images assigned to subobjects. For example, view all images assigned to Devices within a single Rack or Location.

At the moment I can only think of one way and that is to define different queries depending on what device it would be. The downside of this solution would be that it would not be generic.

Next, I can think of building some new filter for Image Attachment type objects.

I would be happy to open a discussion over this topic.

Use case

In our organization, we use images to provide detailed documentation of the condition of equipment. We encounter situations where we would like to see pictures of all the equipment in one room or rack, for example.

Database changes

None

External dependencies

None

Originally created by @drobnymichal on GitHub (Dec 3, 2023). ### NetBox version v3.6.5 ### Feature type New functionality ### Proposed functionality We would like to add the ability to view images assigned to subobjects. For example, view all images assigned to Devices within a single Rack or Location. At the moment I can only think of one way and that is to define different queries depending on what device it would be. The downside of this solution would be that it would not be generic. Next, I can think of building some new filter for Image Attachment type objects. I would be happy to open a discussion over this topic. ### Use case In our organization, we use images to provide detailed documentation of the condition of equipment. We encounter situations where we would like to see pictures of all the equipment in one room or rack, for example. ### Database changes None ### External dependencies None
adam added the type: featurepending closurestatus: under review labels 2025-12-29 20:42:44 +01:00
adam closed this issue 2025-12-29 20:42:44 +01:00
adam commented 2025-12-29 20:42:44 +01:00
Author
Owner
Copy Link

@gdprdatasubect commented on GitHub (Dec 4, 2023):

I always wished for such a thing to exists.
Example: Coworker A uploads a picture of a rack where a device was added to the device itself while coworker B would have uploaded it to the location of the rack instead.

@gdprdatasubect commented on GitHub (Dec 4, 2023): I always wished for such a thing to exists. Example: Coworker A uploads a picture of a rack where a device was added to the device itself while coworker B would have uploaded it to the location of the rack instead.
adam commented 2025-12-29 20:42:44 +01:00
Author
Owner
Copy Link

@gdprdatasubect commented on GitHub (Dec 4, 2023):

Implementation idea: Have a checkbox next to the "image"-headline that enables "child-views", thus everyone can switch to their hearts content:
image

The current table already has content type and parent anyway, so no change seems necessary there.

@gdprdatasubect commented on GitHub (Dec 4, 2023): Implementation idea: Have a checkbox next to the "image"-headline that enables "child-views", thus everyone can switch to their hearts content: ![image](https://github.com/netbox-community/netbox/assets/101808236/dc6a5062-18e5-4387-9b42-f3864297da2a) The current table already has content type and parent anyway, so no change seems necessary there.
adam commented 2025-12-29 20:42:45 +01:00
Author
Owner
Copy Link

@drobnymichal commented on GitHub (Dec 4, 2023):

@gdprdatasubect your idea seems good.

It would be great to add this button also to the list of pictures, which is directly on the page with individual models.

@drobnymichal commented on GitHub (Dec 4, 2023): @gdprdatasubect your idea seems good. It would be great to add this button also to the list of pictures, which is directly on the page with individual models.
adam commented 2025-12-29 20:42:45 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 4, 2023):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (Dec 4, 2023): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 20:42:45 +01:00
Author
Owner
Copy Link

@tippenring commented on GitHub (Dec 8, 2023):

I just came here to look if this feature request was already submitted. To add details from my perspective, here's an example use case. I have switch A in rack B in location C at site D. If switch A has an image attached, that image should show up in the available images for the object rack B, location C, and site D. Ideally each image line item would include the path to the object to which it is attached with URL as well.

@tippenring commented on GitHub (Dec 8, 2023): I just came here to look if this feature request was already submitted. To add details from my perspective, here's an example use case. I have switch A in rack B in location C at site D. If switch A has an image attached, that image should show up in the available images for the object rack B, location C, and site D. Ideally each image line item would include the path to the object to which it is attached with URL as well.
adam commented 2025-12-29 20:42:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 14, 2023):

I think what people are after here is a mechanism to view arbitrary sets of image attachments irrespective of their direct parent object. This would entail introducing a new dedicated list view for image attachments and filters to query by ancestor objects (e.g. rack, location, site).

However, I see limited utility in listing all images attached to descendant objects under the site view. This could potentially be hundreds or thousands of images across many locations, racks, etc. with no convenient mechanism to narrow them down.

@jeremystretch commented on GitHub (Dec 14, 2023): I think what people are after here is a mechanism to view arbitrary sets of image attachments irrespective of their direct parent object. This would entail introducing a new dedicated list view for image attachments and filters to query by ancestor objects (e.g. rack, location, site). However, I see limited utility in listing _all_ images attached to descendant objects under the site view. This could potentially be hundreds or thousands of images across many locations, racks, etc. with no convenient mechanism to narrow them down.
adam commented 2025-12-29 20:42:46 +01:00
Author
Owner
Copy Link

@gdprdatasubect commented on GitHub (Dec 14, 2023):

However, I see limited utility in listing all images attached to descendant objects under the site view.

I see utility exactly there, when you know images where created but not where they where uploaded to exactly, just sort by creation date.

@gdprdatasubect commented on GitHub (Dec 14, 2023): >However, I see limited utility in listing all images attached to descendant objects under the site view. I see utility exactly there, when you know images where created but not where they where uploaded to exactly, just sort by creation date.
adam commented 2025-12-29 20:42:46 +01:00
Author
Owner
Copy Link

@tippenring commented on GitHub (Dec 14, 2023):

I see limited utility in listing all images attached to descendant objects under the site view. This could potentially be hundreds or thousands of images across many locations, racks, etc.

True. Showing all child images under site does not scale well. However, trying to locate an image attached to a device in a rack in a location at a site is not user friendly due to the number of pages a user must click through to locate the desired image(s).

I'm not sure there is a one-size-fits-all solution here. In my use case, showing all child object images scales nicely. Perhaps adding a preference option to list child objects with attached images?

@tippenring commented on GitHub (Dec 14, 2023): > I see limited utility in listing all images attached to descendant objects under the site view. This could potentially be hundreds or thousands of images across many locations, racks, etc. True. Showing all child images under site does not scale well. However, trying to locate an image attached to a device in a rack in a location at a site is not user friendly due to the number of pages a user must click through to locate the desired image(s). I'm not sure there is a one-size-fits-all solution here. In my use case, showing all child object images scales nicely. Perhaps adding a preference option to list child objects with attached images?
adam commented 2025-12-29 20:42:46 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 14, 2024):

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 (Mar 14, 2024): 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 20:42:46 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 15, 2024):

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 (May 15, 2024): 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#8908
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?