-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unracked devices are labeled "None" #21
Comments
After further review, it looks like this issue only happens when the device is unnamed. |
Possible requirement for ability to cope with empty device names, however what field could be used as an identifier - ID is obvious but does not help usability; description would be potentially be too long. |
For consistent user experience, I would expect this to work the same as other rack elevation views, where it shows the device description. There is an open FR for custom labels. If this gets implemented, I would hope it applies here too. netbox-community/netbox#14205 |
NetBox normally shows the Device Type name for unnamed devices in the rack elevation view. |
Oops, yes that’s what I meant. |
netbox-reorder-rack version
v1.1.1
Python version
3.12
Steps to Reproduce
Expected Behavior
It should show the same label as the /dcim/racks/xxx page and respect the labels vs images preference.
Observed Behavior
All the unracked devices are labeled "None" so it's impossible to identify them
![image](https://private-user-images.githubusercontent.com/3991046/342961475-fa104d96-c2fb-43c0-b633-92d203c7c2af.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjI5NTA4MDYsIm5iZiI6MTcyMjk1MDUwNiwicGF0aCI6Ii8zOTkxMDQ2LzM0Mjk2MTQ3NS1mYTEwNGQ5Ni1jMmZiLTQzYzAtYjYzMy05MmQyMDNjN2MyYWYucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgwNiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MDZUMTMyMTQ2WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NzFlNTA0ZmE4NjgwMDU4NjJmNzQyMDQxMmQ1ZWNkNDRiYTliYmNlNzNhMTI0Y2RiNDg1OTgzNjYyZDVjYzg3MCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.Pa5WM8ixEefPc_CDqPHwSCC7UpWyDuUMPtW0nIczMvo)
The text was updated successfully, but these errors were encountered: