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

reserve either 'front' or 'rear' of rack units #6798

New Issue
Closed
opened 2025-12-29 19:45:31 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:45:31 +01:00
Owner
Copy Link

Originally created by @opericgithub on GitHub (Aug 11, 2022).

NetBox version

v3.2.8

Feature type

Change to existing functionality

Proposed functionality

i would like to reopen issue #9090 which was marked as closed due to inactivity, but I find it very useful.

"When adding device reservations for a rack there is no distinction between reserving the front U of the rack, or the rear U of the rack. Not all devices are full depth.

Modify existing reservation mechanism to have the 'Rack Face' and 'Full Depth' options to allow someone to reserve either the front or rear of the rack, and either the full depth or not."

Use case

"If I were to have a cable manager on the front of a rack this device is not full depth. This would leave plenty of room in the rear of the rack to mount something else. Another cable manager perhaps, or a patch panel.

This feature would allow someone to have a non full-depth device occupying rack unit 40 in the front, while reserving rack unit 40 in the rear for another non full-depth device."

Database changes

not sure

External dependencies

not sure

Originally created by @opericgithub on GitHub (Aug 11, 2022). ### NetBox version v3.2.8 ### Feature type Change to existing functionality ### Proposed functionality i would like to reopen issue #9090 which was marked as closed due to inactivity, but I find it very useful. "When adding device reservations for a rack there is no distinction between reserving the front U of the rack, or the rear U of the rack. Not all devices are full depth. Modify existing reservation mechanism to have the 'Rack Face' and 'Full Depth' options to allow someone to reserve either the front or rear of the rack, and either the full depth or not." ### Use case "If I were to have a cable manager on the front of a rack this device is not full depth. This would leave plenty of room in the rear of the rack to mount something else. Another cable manager perhaps, or a patch panel. This feature would allow someone to have a non full-depth device occupying rack unit 40 in the front, while reserving rack unit 40 in the rear for another non full-depth device." ### Database changes not sure ### External dependencies not sure
adam added the type: featurestatus: duplicate labels 2025-12-29 19:45:31 +01:00
adam closed this issue 2025-12-29 19:45:31 +01:00
adam commented 2025-12-29 19:45:31 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 11, 2022):

I'm closing this issue because you've intentionally created a duplicate issue, copying content verbatim from #9090.

The original FR was closed automatically after three months of inactivity because it did not find interest in the community. If you'd like to revisit the proposal, you'll need to bring something new to the table. You're welcome to do so in a new, original feature request.

@jeremystretch commented on GitHub (Aug 11, 2022): I'm closing this issue because you've intentionally created a duplicate issue, copying content verbatim from #9090. The original FR was closed automatically after three months of inactivity because it did not find interest in the community. If you'd like to revisit the proposal, you'll need to bring something new to the table. You're welcome to do so in a new, original feature request.
adam commented 2025-12-29 19:45:31 +01:00
Author
Owner
Copy Link

@opericgithub commented on GitHub (Aug 11, 2022):

Yes, I copied the issue because I didn't want to take credit for other's work.

@opericgithub commented on GitHub (Aug 11, 2022): Yes, I copied the issue because I didn't want to take credit for other's work.
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: duplicate 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#6798
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?