Description: 1/ Open attached document 2/ Select column A 3/ Menu: Data->Filter->Standard Filter ... 4/ Field Name "Column A", Condition "Does not end with", Value: "CTORS" 5/ move with keyboard KEY_DOWN - for example twice down to cell A4 6/ move up to A1 7/ Open Data->Filter->Standard Filter > Standard filter settings are not remembered. Info from Eike: Not really a bug but maybe the handling could be better. What seems to happen is that from the whole-column-selection the actual data range is narrowed down so there isn't a "real" selection remembered. It works if before the first invocation the column is not selected but just the cell cursor placed on a cell of the data (or the data range is selected) so the actual data range is determined from that. Then the filter is remembered regardless whether headers (column labels) are set or not. Maybe worth an RFE. Eike Actual Results: Standard filter settings are not remembered. Expected Results: Standard filter settings are remembered. Reproducible: Always User Profile Reset: No Additional Info: file> https://bugs.documentfoundation.org/attachment.cgi?id=114043 User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0
As there is acknowledgement from Eike, let's set to NEW.
the behaviour is not consistent, as soon as empty cells / rows are contained in the selection above, in or below the data when defining the filter, the filter criteria are remembered by calc (they are stored in 'content.xml' when saving the file), but with a new call of [data - filter - standard filter] only sometimes suggested again, but mostly not. The workflow seems to be that 'filter' first tries to define a range of criteria itself instead of checking if the current selection is in a range for which a filter is already defined. As long as a 'keep filter criteria' option is offered and activated a normal user expects a different behaviour... insofar: 'bug'.
add. - you can! get the filter definition back / get it as suggestion for a new filter, also for ranges with 'empty' on top or bottom or inbetween, if you select the identical range e.g. by keying it in into the 'name box' instead of letting calc try to find it, and for that you have to know what this range was, with ver 7.1 when selecting a whole column for a filter this selection is shrinked to the last cell containing data once you start defining the filter, while a selection of e.g. B1:B1048575 is respected, intentional? but sometimes the filter conditions are messed up, e.g. i observed '= not empty' changed to '= 67' after save-load, whatever that means, but it was written into the filter definition on save ... additional there is mentioned '!empty', but after load '= 67' is evaluated ... whatever it means ... <table:filter-condition table:field-number="0" table:data-type="number" table:value="67" table:operator="!empty"/> and there may be other quirks, not tested, this area needs a rework ...
reproduced with: Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 94d552f94b427f884c004dba5d4619ecf729d605 CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-06-18_13:30:27 Calc: threaded