-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Modern UI: Can't sort columns on statistics page and downloaded report #2449
Comments
@andrewbaldwin44 is this something you could have a look at? |
I wasn't even aware this was a feature! I think it's not very obvious that clicking on table columns will change how the table is displayed. There also appears to be some broken logic with the 'reverse' aspect of this feature:
This code makes it so that when any column is clicked, the order is reversed (i.e. if you want to sort by method, then change your mind and sort by name, you would get reverse alphabetical order) I would propose to do something such as a dropdown for sorting: @cyberw @zifter What do you prefer? Do you prefer I re-introduce the logic from the old UI as is or could we consider an enhancement? |
@andrewbaldwin44 I'm used to a pretty common UX pattern of sorting data in the table by clicking on the header. You can find it everywhere, for example - in Excel, Google Sheets, pgAdmin and etc.
Here is a great example that I find very convenient to use (but lacks some important marks which are showing current ordering): So, as for me, I prefer to reimplement old logic with the latest UX best practices). |
I think I prefer something like:
And a small indicator (up/down arrow) that the column is sorted. But it is not urgent or anything. |
Fixed in 2.18.3! |
Prerequisites
Description
In the new Web UI\Modern UI there is no ability to sort columns in statistics tab. It was possible in the old interface.
Command line
does not matter
Locustfile contents
Python version
3.11
Locust version
2.18.1
Operating system
linux\chrome
The text was updated successfully, but these errors were encountered: