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 image to the Location page view #4758

New Issue
Closed
opened 2025-12-29 19:20:09 +01:00 by adam · 0 comments
adam commented 2025-12-29 19:20:09 +01:00
Owner
Copy Link

Originally created by @jcralbino on GitHub (Apr 13, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v2.11

Feature type

Change to existing functionality

Proposed functionality

Much like we have in the Site option (https://beta.netbox.dev/dcim/sites/24/). where a specific page is shown we have an option for placing images as seen bellow
image

In the new design where a location may represent a room, or some other nested object( room/aisle), it will be interesting to have the same image view there.
When Location represents a DC Room we can use the Images tab to document to room layout.

Use case

When Locations represent specific DC Rooms, or technical rooms the introduction of this field can be used to improve the documentation of the environment:

Images can be used to identify the rack layouts, and details on how to reach the locations and other relevant self documenting images.

Database changes

none

External dependencies

none

Originally created by @jcralbino on GitHub (Apr 13, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v2.11 ### Feature type Change to existing functionality ### Proposed functionality Much like we have in the Site option (https://beta.netbox.dev/dcim/sites/24/). where a specific page is shown we have an option for placing images as seen bellow ![image](https://user-images.githubusercontent.com/44149262/114533443-307fdc00-9c4e-11eb-9397-2e371ee364f8.png) In the new design where a location may represent a room, or some other nested object( room/aisle), it will be interesting to have the same image view there. When Location represents a DC Room we can use the Images tab to document to room layout. ### Use case When Locations represent specific DC Rooms, or technical rooms the introduction of this field can be used to improve the documentation of the environment: Images can be used to identify the rack layouts, and details on how to reach the locations and other relevant self documenting images. ### Database changes none ### External dependencies none
adam added the status: acceptedtype: feature labels 2025-12-29 19:20:09 +01:00
adam closed this issue 2025-12-29 19:20:10 +01:00
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#4758
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?