Created attachment 137436 [details] test ods file The attached .ods file has two columns of data. In the most recent libreoffice version, these two columns are treated separately when doing auto-filtering. Steps to Reproduce: 1. Click on the drop-down list to filter-out "201607" in column B. 2. Click on the drop-down list to observe the items as shown in the filter-list in column A. Current Behaviour: In step 2, all the items are shown in the filtered list. Expected Behaviour: Only 07-2016 is shown in step 2. Further Information: Apparently Calc is treating these two columns as separate data: * If you select cell B1, click the autofilter toolbar icon to remove the autofilter status, only autofilter for column A is removed. It should remove both. * If you select A1:B3692, then click the autofilter toolbar icon to remove the autofilter, then filter on both columns are removed, but if you click the icon to set autofilter again, then filter is set separately again. The ods file was generated using LibreOffice, I am not sure which version was used to create this file.
Version：5.4.2.2 Build ID：22b09f6418e8c2d508a9eaf86b2399209b0990f4 CPU Thread：4; OS: Linux 4.13; UI Rendering：Default; VCL: gtk2; Locale: zh-CN (zh_CN.UTF-8); Calc: single Fedora 26 x64.
Same behaviour already in 3.6.7, but not in 3.3. Arch Linux 64-bit, KDE Plasma 5 Version: 6.0.0.0.alpha1+ Build ID: 1aba1955f161cc112dab80b6b3e78ec7761616fc CPU threads: 8; OS: Linux 4.13; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on November 10th 2017 Arch Linux 64-bit Version 3.6.7.2 (Build ID: e183d5b) Arch Linux 64-bit LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
don't repro in Version: 6.2.0.0.alpha1+ (x64) Build ID: 0b2d153f58c83fb289c96b348631e44e553b1a9a CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2018-11-02_21:11:48 Locale: ru-RU (ru_RU); Calc: threaded but may be is it only Linux problem?
I can repro on Win. I don't know, if Roman understood: when clicking the filter for A in step 2, it should only show ✔07-2016 in the list. This is still the case in 3.3.0, but not in 3.5.0. Version: 6.2.0.0.alpha1+ (x64) Build ID: 317f5f2323b8ff7948c4812faaeb0c2a3b907ce8 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-11-07_02:31:39 Locale: fi-FI (fi_FI); Calc: threaded
Dear Kevin Suo, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
30 months later ... hello @Kevin, you managed to have two overlapping data ranges in your file, one "workshop_consumption", manually set and covering A1:A3692, one "__Anonymous_Sheet_DB__0", such ranges / names are automatically created when you apply an autofilter to a 'not-predefined' range, covering A1:B3692, this was not 'foreseen' by the developers, and or too complex for a programmer to apply a non-conflicting handling for it, thus the two filters collide in a similar manner as if you apply one to column A and one to columen C, by sorting rows touching the other filters range they are in conflict, leftmost column wins?, i'm unsure if 'notabug, user error', or if one can request an error handling option against the construction of such situation ... your original definition: <table:database-range table:name="workshop_consumption" table:target-range-address="'Source Data'.A1:'Source Data'.A3692" table:orientation="column"/> <table:database-range table:name="__Anonymous_Sheet_DB__0" table:target-range-address="'Source Data'.A1:'Source Data'.B3692" table:display-filter-buttons="true" table:orientation="column"/> and it's not the first but a subsequent save of the file as you got - wrong - 'table-orientation' tags ...
(In reply to b. from comment #7) Sorry for the late reply. Now I see that there is a self-defined database range in "Data - Define Range". Not sure when and how this was defined. Deleting that range would solved this problem. Close as NOTABUG.