Skip to content
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

Elevations View Rack Name Number Sort #11014

Closed
brainsfull opened this issue Nov 23, 2022 · 0 comments · Fixed by #11036
Closed

Elevations View Rack Name Number Sort #11014

brainsfull opened this issue Nov 23, 2022 · 0 comments · Fixed by #11036
Assignees
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@brainsfull
Copy link

brainsfull commented Nov 23, 2022

NetBox version

v3.3.8

Python version

3.10

Steps to Reproduce

Using rack names such as 1/1, 1/2, 1/3... 1/10, 1/11, 1/12: When viewing the rack elevations view, the racks are not sorted left to right in numerical order when single digit numbers are used, they show up as 1/1, 1/11, 1/12, etc. whereas in the rack view they sort correctly, showing 1/1, 1/2, 1/3, etc. see below:

image

image

Expected Behavior

In Elevations view, racks are sorted left to right in numerical order, e.g., 1/1, 1/2, 1/3, 1/4, 1/5, 1/6, 1/7, 1/8, 1/9, 1/10, 1/11, etc. like they sort in the rack view.

Observed Behavior

In elevations view, racks are sorted left to right as follows, 1/1, 1/10, 1/11, 1/12... etc.

@brainsfull brainsfull added the type: bug A confirmed report of unexpected behavior in the application label Nov 23, 2022
@jeremystretch jeremystretch added the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label Nov 28, 2022
@arthanson arthanson self-assigned this Nov 28, 2022
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Nov 30, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants