starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 22:03:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Display Rack Reservation text in Rack Elevations #6390

New Issue
Closed
opened 2025-12-29 19:40:08 +01:00 by adam · 5 comments
adam commented 2025-12-29 19:40:08 +01:00
Owner
Copy Link

Originally created by @howard-2020 on GitHub (Apr 21, 2022).

NetBox version

v3.2.1

Feature type

Change to existing functionality

Proposed functionality

Display text for rack reservations in the rack elevation view. We can either use the description field or create a new field called "Label" that would serve strictly as the display text.

Use case

There are certain items that we do not want to create a device for, such as horizontal wire managers, ground bars, etc. We would like to give install technicians a print-out of the rack elevations to work from when installing new equipment in racks. The limitation is that the rack elevations do not list labels or text for reservations. The alternative is to create a device for each item but that is not ideal.

Database changes

Possibly add a "Label" field to the model that has a limit on characters.

External dependencies

None.

Originally created by @howard-2020 on GitHub (Apr 21, 2022). ### NetBox version v3.2.1 ### Feature type Change to existing functionality ### Proposed functionality Display text for rack reservations in the rack elevation view. We can either use the description field or create a new field called "Label" that would serve strictly as the display text. ### Use case There are certain items that we do not want to create a device for, such as horizontal wire managers, ground bars, etc. We would like to give install technicians a print-out of the rack elevations to work from when installing new equipment in racks. The limitation is that the rack elevations do not list labels or text for reservations. The alternative is to create a device for each item but that is not ideal. ### Database changes Possibly add a "Label" field to the model that has a limit on characters. ### External dependencies None.
adam added the type: featurepending closure labels 2025-12-29 19:40:08 +01:00
adam closed this issue 2025-12-29 19:40:08 +01:00
adam commented 2025-12-29 19:40:08 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 25, 2022):

There are certain items that we do not want to create a device for, such as horizontal wire managers, ground bars, etc.

It sounds like you're misusing rack reservations here. Anything that gets installed into a rack should be modeled as a device, not a reservation.

@jeremystretch commented on GitHub (Apr 25, 2022): > There are certain items that we do not want to create a device for, such as horizontal wire managers, ground bars, etc. It sounds like you're misusing rack reservations here. Anything that gets installed into a rack should be modeled as a device, not a reservation.
adam commented 2025-12-29 19:40:08 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Apr 25, 2022):

This use case was recently brought up in #9129

@DanSheps commented on GitHub (Apr 25, 2022): This use case was recently brought up in #9129
adam commented 2025-12-29 19:40:09 +01:00
Author
Owner
Copy Link

@howard-2020 commented on GitHub (Apr 25, 2022):

I agree that I may be misusing the rack reservation intended purpose. However I think it would still be helpful to display text for legitimate rack reservations rather than having to hover over the rack elevation. It looks like the rack elevation would fit about 29 characters without running outside the the rack image. What if you took the first 29 characters of the reservation description and displayed that on the rack elevations? In that case, there would not need to be a new field created.

@howard-2020 commented on GitHub (Apr 25, 2022): I agree that I may be misusing the rack reservation intended purpose. However I think it would still be helpful to display text for legitimate rack reservations rather than having to hover over the rack elevation. It looks like the rack elevation would fit about 29 characters without running outside the the rack image. What if you took the first 29 characters of the reservation description and displayed that on the rack elevations? In that case, there would not need to be a new field created.
adam commented 2025-12-29 19:40:09 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 25, 2022):

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 (Jun 25, 2022): 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 19:40:09 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 25, 2022):

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 (Jul 25, 2022): 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#6390
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?