Allure report timeline graph is sorts features alphabetically instead of numerically so they are not in chronological order.
Context
Jenkins version: 2.263.3
Job type: Freestyle
Allure plugin version: 2.27.0
Allure commandline version: N/A
Problem description
On the Allure report timeline (eg http://qdselenium:8080/job/\<job name>/\<job no>/allure/#timeline ), the y-axis is the features (translated into some simple [0-N] incrementing number; e.g. [thread-feature]).
The problem is that the graph is sorting those alphabetically instead of numerically.
Expected order (numeric sort): [0-1], [0-2].[0-3],[0-4].[0-5],[0-6].[0-7],[0-8].[0-9],[0-10],[0,11]......[0-45],[0-46],[0-47]
Actual order (alphabetic sort): [0-1], ..[0-10],[0,11],[0,12],....[0-2].[0-3],[0-4]........[0-45],[0-46],[0-47],[0-5],[0-6].[0-7],[0-8].[0-9]
So the timeline does not correspond to chronological order, since items [0-5] thru [0-9] are down below 0-47].
Issue
Allure report timeline graph is sorts features alphabetically instead of numerically so they are not in chronological order.
Context
Jenkins version: 2.263.3
Job type: Freestyle
Allure plugin version: 2.27.0
Allure commandline version: N/A
Problem description
On the Allure report timeline (eg http://qdselenium:8080/job/\<job name>/\<job no>/allure/#timeline ), the y-axis is the features (translated into some simple [0-N] incrementing number; e.g. [thread-feature]).
The problem is that the graph is sorting those alphabetically instead of numerically.
Expected order (numeric sort): [0-1], [0-2].[0-3],[0-4].[0-5],[0-6].[0-7],[0-8].[0-9],[0-10],[0,11]......[0-45],[0-46],[0-47]
Actual order (alphabetic sort): [0-1], ..[0-10],[0,11],[0,12],....[0-2].[0-3],[0-4]........[0-45],[0-46],[0-47],[0-5],[0-6].[0-7],[0-8].[0-9]
So the timeline does not correspond to chronological order, since items [0-5] thru [0-9] are down below 0-47].
(Please see also https://github.com/jenkinsci/allure-plugin/issues/171)![image](https://user-images.githubusercontent.com/15637471/123860667-2f2c8a00-d8f4-11eb-8cec-ae98b5e9ccd0.png)
Logs & Traces
Please include any relevant log that could serve to better understand the source of your issue