Created attachment 72950 [details] Sample Document Steps to reproduce with parallel installation of "LOdev 4.0.0.1 rc - GERMAN UI / German Locale [Build ID: 527dba6f6e0cfbbc71bd6e7b88a52699bb48799)]" {tinderbox: @6, pull time 2013-01-10(?)} on German WIN7 Home Premium (64bit) with separate /40 User Profile for Master Branch: 1. Open attached Sample Document 2. 'right click Stheet Tab "Tabelle21" -> Move/Copy Sheet - Copy - Move to End Position <OK> ' > Sheet "Tabelle21_2" created 3. Click an Autofilter pulldown Icon (in Cell "Tabelle21_2.A1") Current behavior: Nothing happens Expected behavior: Autofilter action After 'Save -> Close -> Remove' the Autofilter Icons will have been removed. They should have been removed immediately after creation of new sheet. Operating System: Windows 7 Version: 4.0.0.1 rc
Already [Reproducible] with Server Installation of "LibreOffice 3.3.3 German UI/Locale [OOO330m19 (Build:301) tag libreoffice-3.3.3.1] on German WIN7 Home Premium (64bit) and AOOo 3.4.0 The Appearance is a little different with the old autofilter design, but the result is as in latest versions: no function. So inherited from OOo
Still [Reproducible] with parallel Dev-installation of "Version 4.1.0.0.alpha0+ (Build ID: 61add5c77de1ff963b839020c77f67f14ef07de) TinderBox: Win-x86@6, Branch:master, Pull Time: 2013-03-05_00:20:08" ENGLISH UI / German Locale on German WIN7 Home Premium (64bit) with LODev/4 Masters User Profile NEW because seen in various versions @Spreadsheet Team: Please change Status to ASSIGNED and add yourself to "Assigned To" if you accept this Bug or forward the Bug if it's not your turf (and remove others in team from CC).
** 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 on a currently supported version of LibreOffice (4.4.0.3 or later): https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-02-19
Still reproduced. Win 7 Pro 64-bit, LibO Version: 4.4.1.2 Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432 Locale: fi_FI
** 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 on a currently supported version of LibreOffice (5.0.5 or 5.1.2 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
** 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 on a currently supported version of LibreOffice (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
Still reproducible. Win7. Versions:5.2.7.2 , 6.0.0.0alpha0+
** 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
still reproducible with: Version: 6.3.0.0.alpha0+ (x64) Build ID: 0ae876595e9d9af44fc4d4bc948f8a42d8a27e8d CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; Locale: de-DE (de_DE); UI-Language: en-US Calc: threaded
for the Bug Hunting Session 7.0.0.0.a1+: OP behaviour still repro, same action (copy sheet with defined autofilter) with some other data works ok!, you gain functioning autofilters in the copied sheet, e.g. http://bugs.documentfoundation.org/attachment.cgi?id=56922 from #45958, difference: the file 'source.ods' for this bug has! a 'defined range' which the filter is 'mapped'? to, ('forfilters' defined with '<table:database-range table:name="forfilters" table:target-range-address="Tabelle21.A1:Tabelle21.I9" table:display-filter-buttons="true" table:orientation="column"/>' in content.xml) while 'example.ods' from #45958 doesn't have such a definition, and the filter is mapped to an '__Anonymous_Sheet_DB__0', (such database ranges are defined automatically when you apply an autofilter which doesn't find a defined range to apply to, '<table:database-range table:name="__Anonymous_Sheet_DB__0" table:target-range-address="Hoja1.A1:Hoja1.C1048574" table:display-filter-buttons="true"/>' in content.xml) (forfilters does have a 'xml_tag'? table:orientation="column" which is applied - mostly? - when re-saving a file after save-load cycle and is relevant for other misinterpretations, e.g. https://bugs.documentfoundation.org/show_bug.cgi?id=132488 - dunno if that steps in here too) and! forfilters is a 'defined range' which is a name 'global to a document'? and can: - neither have multiple definitions with different 'scopes' like 'named ranges' may have, - nor is a 'per sheet' definition, as '__Anonymous_Sheet_DB__0' is, which as well can have multiple definitions within one document, one per sheet, thanks @Eike for clarification, thus it's logically impossible to create an identical fully working copy of a sheet with an autofilter defined referencing a 'defined range', unless you e.g. work with new names like e.g. 'forfilters_01' ..., or define and set 'scopes' for defined ranges, or other creative solutions, be aware that the behaviour of #132488 messing around with the .field values might step in for any development and tests of this problem ... i can't judge this reg. very small knowledge about the structures and the code (in fact i just stumbled across this bug when i was looking for the steps in which 'table:field-number=' and 'table:orientation="column"' are defined for the save to file and are read back for runtime representation, any tips for that would be highly appreciated - in #132488 o.c.), all above looked for and said by a 'newbie', i apologize for any mistakes I may have made ... as well i apologize for the length of my contribution, I try to analyze and present the situation clearly, i hope for 'old bugs' such an approach is allowed, maybe you should introduce a new category: 'currently not solveable' and declare such bugs as enhancement requests? simply omitting the filter buttons as suggested by the OP would not be a solution in my opinion, the copy of the sheet would be incomplete,
Reproduced in: Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: de7356c2e0cb099fac396808b5a86a0393b48e5f 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-14_22:38:17 Calc: threaded
*** This bug has been marked as a duplicate of bug 145054 ***