Description: When I add a database range (e. g. from A1:B10) and have something in the subsequent cells of one of the columns (in this example B11 and B12) like SUM() and then filter the database range via Standard or Advanced filter, LibreOffice just extends the database range against my wishes to the row that is completely empty (in this example the range is then A1:B12). The options when defining the database range don't matter. I did this with a new user profile. I do not know whether this behaviour is intended, thus a feature, or a bug. If it is intendet, consider this a enhancement request. Steps to Reproduce: 1. Open new document 2. Mark cells A1 to B10 3. Define a database range via 'Data - Define Range...' for A1:B10 4. The options and the name don't matter 5. Write =SUM(A1:A10) in cell A11 and A12 6. Put the cursor back to cell A1 7. Open the Standard Filter dialogue via 'Data - More Filters - Standard Filter' Actual Results: As soon as the Standard Filter dialogue opens, the database range is extended to A1:B12 Expected Results: My defined database range should not be extended against my wishes. If I define a database range, it has to stay how I defined it. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 6.3.1.2 (x64) Build ID: b79626edf0065ac373bd1df5c28bd630b4424273 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; Locale: de-DE (de_DE); UI-Language: en-GB Calc: CL
already reproducible with: Version 3.6.7.2 (Build ID: e183d5b) but *not* reproducible with AOO 4.1.5
Reproducable with LO 6.2.7.1 (x64) with booth filter types!
(In reply to Oliver Brinzing from comment #1) > already reproducible with: > > Version 3.6.7.2 (Build ID: e183d5b) > > but *not* reproducible with AOO 4.1.5 But in 4.1.5 can you not correct sort the database range!
Dear leander.holtmann, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
*** Bug 159076 has been marked as a duplicate of this bug. ***
Still reproduced in recent trunk build: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 6d71c21890c908225945f0fc3566255ed150f660 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Interesting that just the action of opening the dialog is enough to modify the database range. Not reproduced in OOo 3.3. With linux-64-releases bibisect repo, the earliest version affected is libreoffice-3.4.0rc1. Possibly related to the filter and range work that Markus and Kohei did for LO 3.4, see https://wiki.documentfoundation.org/ReleaseNotes/3.4#Calc Markus and Kohei, it's ancient commits but maybe you have an idea?