Toggle the display of consumed rack units when creating a device #253

Closed
opened 2025-12-29 16:20:10 +01:00 by adam · 7 comments
Owner

Originally created by @jbro209070 on GitHub (Jul 20, 2016).

Is there anyway to only show the available positions in the rack position drop down list instead of showing the full list whether it is occupied or not? I think that would be really useful.

Originally created by @jbro209070 on GitHub (Jul 20, 2016). Is there anyway to only show the available positions in the rack position drop down list instead of showing the full list whether it is occupied or not? I think that would be really useful.
adam added the type: feature label 2025-12-29 16:20:10 +01:00
adam closed this issue 2025-12-29 16:20:10 +01:00
Author
Owner

@jeremystretch commented on GitHub (Jul 20, 2016):

Personally, I like having the occupied units included in the list, as it provides something of a sanity check. But we'll see what others say. (Let's try using the +1 and -1 reactions to vote.)

@jeremystretch commented on GitHub (Jul 20, 2016): Personally, I like having the occupied units included in the list, as it provides something of a sanity check. But we'll see what others say. (Let's try using the +1 and -1 reactions to vote.)
Author
Owner

@bellwood commented on GitHub (Jul 20, 2016):

I think this would probably be best addressed with a user definable configuration.

I'm going to presume we'll have many things that work for some and not for others and if they are somewhat trivial to implement (see #285) and don't creep the scope badly it would be beneficial for the user base to have them.

@bellwood commented on GitHub (Jul 20, 2016): I think this would probably be best addressed with a user definable configuration. I'm going to presume we'll have many things that work for some and not for others and if they are somewhat trivial to implement (see #285) and don't creep the scope badly it would be beneficial for the user base to have them.
Author
Owner

@Gelob commented on GitHub (Jul 22, 2016):

Having mentioned this on IRC I understand the reasoning of the way it is but at the same time would like to have the option.

@Gelob commented on GitHub (Jul 22, 2016): Having mentioned this on IRC I understand the reasoning of the way it is but at the same time would like to have the option.
Author
Owner

@mjclancyau commented on GitHub (Jul 26, 2016):

Maybe just a format change (e.g. bold) on currently occupied RUs? Or some sort of flag character or icon?

@mjclancyau commented on GitHub (Jul 26, 2016): Maybe just a format change (e.g. bold) on currently occupied RUs? Or some sort of flag character or icon?
Author
Owner

@jeremystretch commented on GitHub (Jul 26, 2016):

@mjclancy83 Unfortunately, there's not much we can do as far as styling the stock pull-down widget. We'd have to replace it with a custom widget, which probably isn't worth the effort.

@jeremystretch commented on GitHub (Jul 26, 2016): @mjclancy83 Unfortunately, there's not much we can do as far as styling the stock pull-down widget. We'd have to replace it with a custom widget, which probably isn't worth the effort.
Author
Owner

@bellwood commented on GitHub (Jul 26, 2016):

I will note on Mac's dropdown styles (background colors) are not visible so text styling is really the only option if we're to change the look.

I would honestly make a setting to hide consumed U's when adding a device to a rack and let the administrator decide but ultimately it may need to be a user level setting (what works for the admin doesn't always work for the end-user)

@bellwood commented on GitHub (Jul 26, 2016): I will note on Mac's dropdown styles (background colors) are not visible so text styling is really the only option if we're to change the look. I would honestly make a setting to hide consumed U's when adding a device to a rack and let the administrator decide but ultimately it may need to be a user level setting (what works for the admin doesn't always work for the end-user)
Author
Owner

@jeremystretch commented on GitHub (Feb 1, 2017):

Closing this out as I don't see any progress being made on it. However, we're sure to implement something along this vein in a (distant) future release once the web UI becomes API-driven.

@jeremystretch commented on GitHub (Feb 1, 2017): Closing this out as I don't see any progress being made on it. However, we're sure to implement something along this vein in a (distant) future release once the web UI becomes API-driven.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#253