Show reservation descriptions in rack model #6520

Closed
opened 2025-12-29 19:41:55 +01:00 by adam · 4 comments
Owner

Originally created by @themmini on GitHub (May 30, 2022).

NetBox version

v3.2.2

Feature type

New functionality

Proposed functionality

Have reservation descriptions show in the rack model

Use case

When using the DCIM feature I found that rack reservations are a great way to get some temporary registration of what is installed in a rack. At least before you are able to properly model the device types you eventually want to use.

However if you use rack reservations the rack model just shows the rack units as occupied. In my opinion it would be much nicer if it would show the description from the reservation as well.
60553359-418a8200-9d33-11e9-895f-9f2b1baec98e

Database changes

No response

External dependencies

No response

Originally created by @themmini on GitHub (May 30, 2022). ### NetBox version v3.2.2 ### Feature type New functionality ### Proposed functionality Have reservation descriptions show in the rack model ### Use case When using the DCIM feature I found that rack reservations are a great way to get some temporary registration of what is installed in a rack. At least before you are able to properly model the device types you eventually want to use. However if you use rack reservations the rack model just shows the rack units as occupied. In my opinion it would be much nicer if it would show the description from the reservation as well. ![60553359-418a8200-9d33-11e9-895f-9f2b1baec98e](https://user-images.githubusercontent.com/11536761/170904105-ddab035c-b5c1-4f6f-b7a1-8ddeab860195.png) ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 19:41:55 +01:00
adam closed this issue 2025-12-29 19:41:55 +01:00
Author
Owner

@jeremystretch commented on GitHub (May 31, 2022):

The description field for a rack reservation is intended to hold more than a single device name, and would not easily fit into the rack elevation drawing in most cases.

@jeremystretch commented on GitHub (May 31, 2022): The description field for a rack reservation is intended to hold more than a single device name, and would not easily fit into the rack elevation drawing in most cases.
Author
Owner

@themmini commented on GitHub (Jun 1, 2022):

The description field for a rack reservation is intended to hold more than a single device name, and would not easily fit into the rack elevation drawing in most cases.

Not the full description just an optional ‘label’ field or ‘display’.

I also note in the example you can clearly see the difference between the different reservations. We’re currently you can also see there’s some reservations in the rack layout with no indication if they are many reservations or just one without hovering over each RU.

@themmini commented on GitHub (Jun 1, 2022): > The description field for a rack reservation is intended to hold more than a single device name, and would not easily fit into the rack elevation drawing in most cases. Not the full description just an optional ‘label’ field or ‘display’. I also note in the example you can clearly see the difference between the different reservations. We’re currently you can also see there’s some reservations in the rack layout with no indication if they are many reservations or just one without hovering over each RU.
Author
Owner

@jeremystretch commented on GitHub (Jun 1, 2022):

Your proposal states:

Have reservation descriptions show in the rack model

If you intended something different, please update it above to reflect your intended change(s). Be sure to note the relevant database changes as well.

@jeremystretch commented on GitHub (Jun 1, 2022): Your proposal states: > Have reservation descriptions show in the rack model If you intended something different, please update it above to reflect your intended change(s). Be sure to note the relevant database changes as well.
Author
Owner

@jeremystretch commented on GitHub (Jun 17, 2022):

Closing this out as no further clarification has been made to the proposed change.

@jeremystretch commented on GitHub (Jun 17, 2022): Closing this out as no further clarification has been made to the proposed change.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#6520