-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
lexicographical sorting order of device bays #243
Comments
@jeremystretch this should have been ... sorted ... in #9 right? |
That fix only applied to interfaces and interface templates. We could use an additional, more generic natural sort manager for this sort of thing. The same problem applies to device names, console ports, etc. |
possible fix for #243 generic sorting for device bays
Merged #248 which should address this. Need to |
After updating today I still see that all Device interfaces I've created are ordered incorrectly. Seems very Random. Device Type Template Interfaces are ordered OK, but any devices created from them get a random sort. Does this fix apply to devices you've already created? |
The same ordering is used for both Interfaces and InterfaceTemplates. This issue is only for |
OK, so a different ordering for interfaces regardless of on the device or [image: Inline images 1] If you would prefer I could log this as a separate issue, so you can track Chris Jenner On 14 July 2016 at 17:48, Jeremy Stretch notifications@github.com wrote:
|
possible fix for netbox-community#243 generic sorting for device bays
…d DeviceType objects (except interfaces)
Minor issue but slightly annoying. If I create say a blade chassis container and add device bays with the names Server[1-16]. It creates them as expected, but then displays the sort order in a technically correct, but unrealistic way. aka Server1, Server10, Server11... Server16, Server2.
The text was updated successfully, but these errors were encountered: