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

rack "side" view + actual device depth #8540

New Issue
Closed
opened 2025-12-29 20:37:56 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:37:56 +01:00
Owner
Copy Link

Originally created by @ITJamie on GitHub (Aug 31, 2023).

NetBox version

v3.5.9

Feature type

Change to existing functionality

Proposed functionality

a new field would exist on devicetype models which knew the actual depth of a device, this could be used to calculate if a device can fit into a rack & if it would be full or partial depth in that rack.

along with the front/rear elevation view of a rack a "side" view would be useful. this would be especially useful on two post racks which can sometimes need to be balanced (not have all heavy devices hanging to one side).

Use case

  • quicker ability to visualize a rack
  • potentially flag where devices are too long to fit into a rack (device depth vs rack dimensions)
  • we could potentially drop the current depth boolean in the future and instead calculate full depth vs half depth based on rack depth and device type dimensions.

Database changes

add a new device_depth (int) field to device type model

External dependencies

n/a

Originally created by @ITJamie on GitHub (Aug 31, 2023). ### NetBox version v3.5.9 ### Feature type Change to existing functionality ### Proposed functionality a new field would exist on devicetype models which knew the actual depth of a device, this could be used to calculate if a device can fit into a rack & if it would be full or partial depth in that rack. along with the front/rear elevation view of a rack a "side" view would be useful. this would be especially useful on two post racks which can sometimes need to be balanced (not have all heavy devices hanging to one side). ### Use case - quicker ability to visualize a rack - potentially flag where devices are too long to fit into a rack (device depth vs rack dimensions) - we could potentially drop the current depth boolean in the future and instead calculate full depth vs half depth based on rack depth and device type dimensions. ### Database changes add a new device_depth (int) field to device type model ### External dependencies n/a
adam added the type: featurepending closure labels 2025-12-29 20:37:56 +01:00
adam closed this issue 2025-12-29 20:37:56 +01:00
adam commented 2025-12-29 20:37:56 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Aug 31, 2023):

related: #13555

@ITJamie commented on GitHub (Aug 31, 2023): related: #13555
adam commented 2025-12-29 20:37:57 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 30, 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 (Nov 30, 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:37:57 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 30, 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 (Dec 30, 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.
adam commented 2025-12-29 20:37:58 +01:00
Author
Owner
Copy Link

@AnythingOverIP commented on GitHub (Mar 12, 2024):

Duplicate of https://github.com/netbox-community/netbox/issues/1627

@AnythingOverIP commented on GitHub (Mar 12, 2024): Duplicate of https://github.com/netbox-community/netbox/issues/1627
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#8540
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?