-
Notifications
You must be signed in to change notification settings - Fork 147
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
Unify article sorting across views #1068
Comments
Lists from the supplier are often sorted by article number. Apart from that, I think harmonising this is great for everyone. |
Good point. Perhaps the best option for that case would be to introduce two
If you only want a different sorting for receive, you could still use the sorting feature there each time. Another option could be to make each list sortable, But for PDFs/CSVs, we would have to add more options ... |
I like your two kinds of lists. |
I find it quite inconvenient at times that articles are sorted differently in different menus/views.
For example, some of our suppliers print out the order PDF and use it as a basis for a delivery note / invoice (they add the actual prices or cross out articles which they can't deliver), or they write their own invoice in the same order.
When comparing such an invoice to the article PDF and/or the accounting menu, you have extra work to find each article in each list. If they were sorted in the same way, lists would be much easier to compare.
By looking at the views (in the frontend, not in the code) I determined there are 3 general sortings used:
Here's an incomplete list of the sortings used by each view:
Since (category, article name) is the most commonly used sorting, and there's good reason to sort articles by category at least in order placement views, I'd propose to apply it to all views, resulting in the following changes:
Or do you think there's any good reason to prefer sorting by order number in fax PDF / receive, and apply this to accounting, fax CSV, group/article/matrix PDF etc. instead?
The text was updated successfully, but these errors were encountered: