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

Show or link front / rear image from device type to device #8028

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

Originally created by @blindzero on GitHub (May 10, 2023).

NetBox version

v3.5.1

Feature type

New functionality

Proposed functionality

A front / rear image on a device type should be easily accessible from a device by a link or even be shown.

Use case

Usability improvement, less back and forth navigation.

Database changes

No response

External dependencies

No response

Originally created by @blindzero on GitHub (May 10, 2023). ### NetBox version v3.5.1 ### Feature type New functionality ### Proposed functionality A front / rear image on a device type should be easily accessible from a device by a link or even be shown. ### Use case Usability improvement, less back and forth navigation. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 20:31:27 +01:00
adam closed this issue 2025-12-29 20:31:27 +01:00
adam commented 2025-12-29 20:31:28 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (May 10, 2023):

On the device page, you get the full rack view which displays the images as well. Does that not suffice here?

@abhi1693 commented on GitHub (May 10, 2023): On the device page, you get the full rack view which displays the images as well. Does that not suffice here?
adam commented 2025-12-29 20:31:28 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 10, 2023):

You can also just follow the link to the device's device type. I see no reason to embed the device type elevations within the device view, which is already quite busy.

@jeremystretch commented on GitHub (May 10, 2023): You can also just follow the link to the device's device type. I see no reason to embed the device type elevations within the device view, which is already quite busy.
adam commented 2025-12-29 20:31:28 +01:00
Author
Owner
Copy Link

@blindzero commented on GitHub (May 10, 2023):

The device type is some template. So the important instance is the device itself, right?
Hence, a dedicated front / rear attachment is more important on the device itself, but not existing there.
This would be ok if the information from the template would be accessible more easily. Other tools often work with modal displays etc in these cases.

@blindzero commented on GitHub (May 10, 2023): The device type is some template. So the important instance is the device itself, right? Hence, a dedicated front / rear attachment is more important on the device itself, but not existing there. This would be ok if the information from the template would be accessible more easily. Other tools often work with modal displays etc in these cases.
adam commented 2025-12-29 20:31:28 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 10, 2023):

The device type is some template. So the important instance is the device itself, right?

The front & rear images are assigned to the device type, and thus identical for every instance of it. Showing them on each instance is redundant and unnecessary.

@jeremystretch commented on GitHub (May 10, 2023): > The device type is some template. So the important instance is the device itself, right? The front & rear images are assigned to the device type, and thus identical for every instance of it. Showing them on each instance is redundant and unnecessary.
adam commented 2025-12-29 20:31:29 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 9, 2023):

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 (Aug 9, 2023): 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:31:29 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 9, 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 (Sep 9, 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#8028
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?