Autofilter sorting doesn't affect non autofiltered columns, there is no warning, the result is a complete mess up of a spreadsheet.
Big, big mess.
Solution: for the Autofiler function, just copy MS Excel behaviour in every aspect. It's perfect.
Steps to Reproduce:
1) Fill in three columns with sortable data
2) Setup three column labels (let's say A, B, C)
3) Select only A and B column labels (leave the C column out of the selection)
4) Select Data/Autofilter, to setup autofilter labels on A and B, but not C.
5) Click on the A lable
6) Select Sort/Descending (or Ascending, depending on how you sorted data in the first place)
Only the A and B column get sorted, while the C column sticks to the original sorting. Raws data alignment is broken. Big mess.
7) Select a cell in the C column
8) Select Data/Sort...
Autofilter labels on A and B columns get lost.
Just copy MS Excel behaviour. It's perfect.
- Raws alignment should never be broken without warning
- Autofilter labels should never disappear after a sorting operation
- Sorting should always affect either the whole spreadsheet, or the selected columns/group of cells.
User Profile Reset: No
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0
Users always have the freedom to create a mess ;)
But you propose a warning such as
"You've set a filter for rows XYZ, that you are now going to use.
Mind that the row AB next to it, is not included and will be left out of
Do you want to continue or do you want to extend the filter to include
[continue] [adapt filter]  do not show this warning again"
/me a bit worried about all other areas and scenarios that we 'should' cover with like wise warnings..
(In reply to Cor Nouws from comment #1)
> Users always have the freedom to create a mess ;)
Nope. Please, go to step 4, then try selecting whichever area you want (column, group of cells, or select all) then apply step 5 and 6, look what happens. You have no control whatsoever on the area to be sorted: sorting always applies to all columns with the autofilter label, and never to the other columns, no matter which area you selected before sorting. So, if you wanted to create *your* mess, you couldn't. It's the program that *always* create the mess of its own choice.
> But you propose a warning such as
> "You've set a filter for rows XYZ, that you are now going to use.
Nope. I've set a sorting order, not a filter. The behaviour of the function here should be coherent with the Data | Sort ascending and Data | Sort descending functions behaviour.
> Mind that the row AB next to it, is not included and will be left out of
> the action.
Nope. I've set a sorting order for column A, either all columns should be affected, or just column A. Warnings and selection extensions should be exactly the same as for Data | Sort ascending and Data | Sort descending.
> Do you want to continue or do you want to extend the filter to include
> column AB?
> [continue] [adapt filter]  do not show this warning again"
Nope. I just don't want to have *two* different sorting function, with two different and incoherent behaviours, one of them always breaking records by design, and without warning.
I don't like MS Excel, and I don't use it, bit this is very very bad design in LibreOffice.
it isn't a bug but expected behaviour.
Eike, may be you have some opinion about this?
confirmed here in 220.127.116.11
I second the reporter's remark regarding the inconsistency ("Warnings and selection extensions should be exactly the same as for Data | Sort ascending and Data | Sort descending.")
I do not see this behavior as a bug. It is up to the user to select all the columns that are linked. In case you can have several independent blocks of data sharing the same rows, it's clear that Calc can't know what columns are linked to the column in which the sort is performed.
Best regards. JBF
The bug reporter and me have given our reasons why we consider this a usability bug.
In contrast, under which practical use case do you expect a user to deliberately destroy a linkage between the columns of one row in a table?
If there is a significant use case I have not seen before you may be able to convince me :-)
Same warning / offering similar selection extension as in Sort may make sense. However, note that AutoFilter can be applied starting at the current selection, so extending the range above might not be wanted at all.