UI sorting

[xdml]

Originally the ticket list was a table with headers where sorting had been implemented by adding clickable table headers.

After the UI changed, now there is one row with headers, but tickets itself are formatted in blocks instead table rows:

Personally I think it is not intuitive and may confuse lot of users.

So, probably better will be to use <select> instead, like:

OR tabs, like:

I personally like tabs more, but we will be limited with space, so for many sorting options <select> will be better choice.

[evereux]

I like it. Agreed. I had planned on the same thing as I thought the sort bar took up too much space. I can do that unless it's something you'd like to do.

…

On 17 November 2019 08:26:13 xdml ***@***.***> wrote: Originally the ticket list was a table with headers where sorting had been implemented by adding clickable table headers. After the UI changed, now there is one row with headers, but tickets itself are formatted in blocks instead table rows: Personally I think it is not intuitive and may confuse lot of users. So, probably better will be to use <select> instead, like: OR tabs, like: I personally like tabs more, but we will be limited with space, so for many sorting options <select> will be better choice. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[xdml]

My preference is to more focus on backend as to frontend, as I have minimal experience with UI design.

[evereux]

Same for me.

[xdml]

I'll pick this one. My suggestion is to do it like <select> on the right side of page on the same "row" as paginator at top.

[evereux]

Sounds good. I was going to add it to the search form but this is better.

[xdml]

I think this can be closed now.