-
Bug
-
Resolution: Unresolved
-
Minor
-
None
In the views select list, the sort order is currently case-sensitive. For example, the following entries would currently be sorted:
Alpha
Beta
Gamma
aardvark
gorilla
Where the ideal sorting would be:
aardvark
Alpha
Beta
Gamma
gorilla
The list should have a natural sort order that is case insensitive.
It should be noted that case-insensitive ordering is Jenkins' behavior by default when displaying tabs, so the current behavior of the select list differs from that of Jenkins. Ultimately, the sorting should match how Jenkins orders the tabs when the plugin is not installed.
[JENKINS-8860] Views select list sorting should be case-insensitive
Since it falls back on Jenkins' standard view sorting, can you provide some insight on why it would order differently than the Jenkins tabs (when the plugin is not installed)? If I reassign to core, I'd want to be able to explain the difference, I suppose.
@Rob
For me, this issue is currently fixed (using Jenkins v1.446).
Do you confirm that?
@evernat - We've got Jenkins 1.451 installed and the issue is still present. The list sill shows all uppercase projects first followed by all lowercase projects, each portion itself sorted alphabetically.
I tried creating a new lowercase-named view to see if it would insert it into the uppercase portion (in case the list was static and only updated when items were inserted), but the new lowercase view was displayed in the lowercase portion with the rest of the lowercase views.
Added a new view in Jenkins 1.451 to test whether or not issue was fixed.
The new view, titled "lowercase", ought to have been inserted after the two existing uppercase "Li..." items, but instead was added after all of the uppercase items in the list.
I attached a screenshot.
Hi Rob,
Thanks for the screenshot. I see now that I was not testing the same thing.
I would propose polishing this issue to resolve a more generic issue than case-sensitivity:* alphanum sorting*, that why I added it under https://issues.jenkins-ci.org/browse/JENKINS-44119
While I could implement this, I think it is not such a great idea to do within the locality of the plugin. This plugin doesn't sort the views at all, it falls back to the way standard view sorting is handling in Jenkins. Perhaps this could be re-assigned to core for evaluation? Otherwise, it should be closed.